Custom Rewrite Slug not working

Have you tried flushing the rewrite rules yet, by visiting the permalinks page?

Nothing in the 4.2.1 update should have had an effect on this, 4.1.x to 4.2 could have, but I haven’t had anything or seen anything confirmed. Otherwise, it would lay in the changes in our plugin, for which we can look at the changelog to figure out what may have been the source for your case. However, I’m hopeful the permalinks flush will be enough.

Yes, flushed rewrite rules by permalinks page and still same.

Today I reverted back to 1.0.5 and Custom slug are working. I will stick to version 1.0.5. for now until someone confirms this issue.

Thnx

A question that may shape my next reply. Do these urls have taxonomy term slugs in them at all for intended taxonomy archives with the post type?

Not sure if understand. Not using archive for cpt (has_archive=false).

I have taxonomy that is called same as cpt. My cpt is called ‘custom_tours’ (custom rewrite slug = ‘tours’) and i have taxonomy called ‘custom_tours’ (no custom rewrite slug).

I am expecting url like,

https://site.com/tours/slug-of-cpt

but i get with the_permalink(),

https://site.com/custom_tours/slug-of-cpt

Sounds like it’s interpreting the request as a post type instead of a taxonomy at this point. Which would play into the one change I have in place for 1.0.8.

Could you try out https://github.com/WebDevStudios/custom-post-type-ui/archive/master.zip and see if that helps with this issue?

Deactivate your current one before activating this one, or else you’ll have function name clashes.

Yes. It is working ??

Can you explain?

Order of registration essentially. 1.0.7 has both post types and taxonomies registered on init at priority 10, 1.0.8 is bumping taxonomies up to priority 9. 1.0.6 and such had taxonomies on 10, and post types on 11, and that was causing post type issues. I am hoping this doesn’t reintroduce those, to be honest, because I’m not sure how to handle some people needing certain registration order and others needing some other one.

Maybe some kind of hidden plugin option to set prirotiy order.

I can work with 1.0.5. until update of 1.0.8.

I think that this issue is solved.