404 errors on version 1.0.3
-
Hi Michael
Unfortunately I’m getting 404 errors on my cpt after updating to version 1.0.3. I was hoping that the upgrade errors with previous version might be solved with this one.
I have tried to re-save the CPT and I have re-saved my permalink setting, but still no luck.
I do have a dev site if you would like me to try some things.
-
If you’re willing to let me into the dev site, set up a user that uses michael @ webdevstudios . com for the email and it’ll reach me.
Hi Michael….I’m afraid I’m in the same boat here on a project where one of my CPT’s fails after updating to your latest version of CPT UI. This has been the case for the last few versions and I keep rolling back and procrastinating reaching out to you.
In any case, I sat down tonight and tried to update to your latest version 1.0.3….and still no luck. SO…I chased it down a bit myself and revealed that my issue seems to be the fact that custom taxonomies that I’ve assigned to custom post types are being lost.
I’ve read through a number of other support threads here and tried things like visiting the “Permalinks” page to flush the rewrite rules…and I even loaded/saved each of the custom post types and taxonomies in my site…no luck.
However…if I manually re-attach my taxonomies to the CPTs, then things come back to life. Certainly I’ll go that route if I need to, but thought I might be able to help you troubleshoot this issue in the meantime.
I have a working DEV version of my project with CTP UI at 0.9.5….would you like me to add you as a user? Perhaps you can look at how I have things configured and see why those cpt/taxonomy connections are being dropped upon upgrade.
Please advise..thx! rp
rpetersnmt, part of the issue that you likely experienced by trying from 1.0.0-1.0.2 involves the fact that I had to change some array keys in the newly stored option. Chances are the option was never cleared out after you tried another new bug fix release, and thus was still technically “broken”.
So I’m curious how things will go for you moving from 0.9.5 straight to 1.0.3, with a freshly converted new option.
I also have 1.0.4 coming up soon, once I can confirm one thing with hierarchical rewrites in taxonomies, but that may not be till later tonight or tomorrow, depending on how busy I am today.
Thanks for the message/support here. I’m afraid going straight from 0.9.5 to 1.0.3 still resulted in breakage. Because I host with WPEngine, I’ve left the “Development” site at 0.9.5 and just made copies on my “Staging” to test. I can make you a user there too if you’d happen to like to test.
I’m not in a HUGE rush to get this updated since everything is working fine on 0.9.5, so if you’d like to use this as an opportunity to troubleshoot, please let me know. 🙂
Otherwise, I’ll wait until 1.0.4 and try it again, fresh from 0.9.5.
Thx!
Yeah, let me get 1.0.4 out the door and I’ll try to loop back over here. Feel free to post a new reply to remind me as well if I am silent too long.
Hi Michael, Any update on getting 1.0.4 out? We’ve got a big site that’s having the same issues with 404’s.
Not quite yet, Laura, but the night is young and I’m a night owl, so I’ll probably push it out tonight yet.
Once you see it come in and update, make sure to flush your rewrite rules and let me know if there are still issues going on.
Worst case scenario, you’re able to revert still, back to 0.9.5 and regain what you had before the update.
Hi Michael…I saw that you pushed out 1.0.4…thanks for continuing to work on clearing out these lingering bugs.
I tried to update from 0.9.5 to 1.0.4 and after doing so (on a dev copy) I was still left with a loss of associated taxonomies. My CPTUI-created CPTs are no longer “connected” to their custom taxonomies and this ends up breaking a number of things on my soon-to-launch site.
Any more thoughts? I understand what I need to do to fix it (just re-associate the taxonomies) but I’m stalling to see if you’d like me to help you troubleshoot. I feel like I have a situation here that could be helpful (problem site and easy to clone “dev” for troubleshooting). As soon as I apply the fix to my production site this opportunity will go away.
Anyway…I’ll stall a couple more days before fixing…..but please do let me know if I can help. 🙂
Ross
Go ahead and re-associate the taxonomies to the post type and hit save. I am comprehending the behavior, so I can do testing on my own for that one. I’d rather you get yours fixed at the moment.
Thank you for your willingness to help though, it is appreciated and noted.
Okay…I updated, re-associated and she’s fixed up. Thx!
Hi ! i have WP 4.1.1 and Custom Post Type UI 1.0.4.
i configured the slug /training/ for a custom post type, but rewriting does not work.
Standard slug for posts is /blog/..when i try /blog/training/ then it shows the page.
I tried everything i found in this forum. No idea, what to do next.
Any idea ? Thanks Eduard
Calormedia, what do you have for your withfront setting? I have to wager you may be on multisite as well, since that’s usually where the /blog/ prefix comes from.
The topic ‘404 errors on version 1.0.3’ is closed to new replies.