PLEASE POST A WARNING ON THE PLUGIN PAGE

Thank you for your feedback. I’m still trying to pinpoint exactly where it’s failing, because I had no issues with my testing, though it didn’t have as much content as other, existing users, likely have. I really wish more people responded to my calls for beta testing, because that would have helped me out.

Do you have a dev site for this client site still that you’d be willing to try things on to help me pinpoint the issue points?

You’re welcome for the retained database values, I knew this was a huge update and I wanted to retain roll-back ability, in cases of issues.

Thanks Michael

I clearly missed the call for beta testing, otherwise I would’ve tried. I’m slightly more designer than developer but would / will help out if I can.

Unfortunately I don’t have the dev site anymore, due to other issues and switching servers days before launch.

I will see if I can do that with one of my other client sites.

And again, thanks for the retained DB values. A little bit of thinking ahead, but a lot of life-saving!

Will keep an eye on this forum, and post anything too if I can help

I had exactly the same issue as markgt, there should be a warning on the plugin page that it could cause problems.

Thank you markgt, your solution saved me time working out what was up.

Apart form this hiccup your plugin as proved itself as the best out there, thank you Michael for you good work ??

For what it’s worth the original upgrade notice did say it was a major update, but the issues that emerged quickly weren’t anticipated either, and were serious enough that I made 0.9.5 the same as 0.8.5 with a higher version number to prevent more reported issues coming in until I can get things fixed. I’ve requested saved option data from a number of people to help me debug what’s going on and what’s failing where, and hopefully that proves successful the next time.

duckonwater, would you be willing to test a currently patched version to see if it clears up the issues?

I can provide a zip file that you can install that will upload the hopefully fixed version alongside 0.9.5 so you can easily switch back if still not working yet.

Preferably on a dev copy of your site if possible.

Sorry Michael, I probably came across a little rude before.
Didn’t mean to sound ungrateful, its super cool that you provide all this, AND free of charge! ??

Sure be happy for us to test the patched version, will be on local dev, thats no prob.

Just send to enquiries (at) duckonwater.co.uk

Cheers!

No rudeness implied. I was more in a panic over what was going on anyway ??

https://github.com/WebDevStudios/custom-post-type-ui/archive/master.zip

Download and install the plugin in the zip above. It should make “custom-post-type-ui-master” for the folder if I recall right, so you could install it alongside 0.9.5. Best to deactivate 0.9.5 first before activating this copy, which should be labeled 1.0.0 now. Once activated, flush the rewrite rules and test.

I appreciate the patience and help.

Thanks for the patch. Thankfully, I test everything before I change a live site.

*Gone to check this out*

Anyone in this thread still having issues? Or are we all good to mark this one resolved?

Hi Michael,

I just updated from 0.8.5 to 1.0.3 and now all custom post types and taxonomies are missing :/
I tried it on a sandbox fortunately.
What could be wrong WP is V4.1.1

Regards,
Rasmus

Rasmus, did you flush the permalinks after updating? Just visiting the permalinks page should be enough to trigger that.

Hi Michael,
Thank you for the feedback, I think it’s working now ??

*thumbs up*

I’m still having the 404 issue. I’ve visited the Permalinks page to flush the rules, and made sure all post types Has Archive = true. What are the next steps I should take to resolve this issue? Thanks.

Arkadaemos, I went through each of my CPTs from within CPT UI and clicked the “Edit Post Type” button on each, then went to Settings > Permalinks and hit the “Save Changes” button. Everything is working for me again.