3rd time I’ve had taxonomy issues reported, but I’m not sure why because as far as I’ve known, taxonomy archives have never been a thing with WordPress. They do archives for individual terms within the taxonomy, but never a complete archive of posts for all terms within the taxonomy.
Would you be willing to send me your export settings as well as which permalink settings you are using? I am curious if I can recreate locally and see if there’s anything I can do about it.
Thread Starter
mmink
(@mmink)
I’m using Custom Structure permalink settings:
/%category%/%postname%/
The export does not seem to be working correctly. None of my taxonomies are included.
Thread Starter
mmink
(@mmink)
Oops. I didn’t realize there are two exports. How would you like me to send you the export settings?
Based on some stuff from a previous similar issue, could you check your post type settings and confirm if the taxonomies are properly associated still? If not, could you re-check the appropriate values, save, and then check the frontend links again?
If that still doesn’t work, then email me the export settings to michael @ webdevstudios . com
Thread Starter
mmink
(@mmink)
The 404 errors don’t occur in 1.0.7. Thanks for the update — that seems to have done the trick. š
Odd, but I’ll take it š
1.0.7 didn’t do anything except do some url hardening for security purposes, but like I said, I’ll take it if it’s working for you now.
Thanks for the update mmink.
Thread Starter
mmink
(@mmink)
All was well until the latest WordPress updates: 4.1.4 and 4.2.1. Custom post type archives work, but the custom taxonomy archives do not.
Do you think a new version of CPT UI will be needed for compatibility with WP 4.2.1? If not I’ll email you my export settings.
No, those are just security releases that wouldn’t introduce any compatibility issues with our plugin. The changes shouldn’t have done anything to core functions that we use either.
Sorry for the delay in response to the email.
Biggest thing I’m seeing that could be a contributing issue to the taxonomy errors are the rewrite slugs: recipes\/occasions, recipes\/courses, good-reads\/types. I have to wonder if those are messing with the query, and returning no results. Not sure honestly why they were potentially working before, but it does look like you have similarly named post types as well.
Thread Starter
mmink
(@mmink)
Following other support topics (https://ww.wp.xz.cn/support/topic/overlapping-post-type-and-taxonomy-slugs-no-longer-work?replies=6) — I tried the following tip from you:
In the main custom-post-type-ui.php file, find the line
add_action( 'init', 'cptui_create_custom_taxonomies' );
around line 235, and change it to
add_action( 'init', 'cptui_create_custom_taxonomies', 9 );
Changing the priority to 9 from the default 10 fixed my issue.
Cool, interesting as well. Not something I didn’t anticipate as a possible thing. At some point I moved the post types to priority 11 because taxonomies were having issues when registered at the same priority, but then post types were having issues, so I moved that back to 10, and the taxonomies apparently struggled a bit now. So I may have to move them to 9.
Just wanted to add another confirmation on this. The fix for line 235 worked in my case as well.
Gonna put it in a 1.0.8 release, probably next week.
