Updating Plugin lost post types

What version are you updating from?

I’m curious if there’s some sort of slug change somehow occurring and the actual post data is still present in the database. If there is somehow a changed slug for what gets registered, then it’d appear like everything got lost, but actually is still available once re-matched up.

For what it’s worth, we don’t touch the posts table ever with an update process, with our code. Only time we come close is when switching post type slugs and we provide a chance to convert post types for found posts from the old slug. That’s a manual choice by the user though.

Oof, yeah, that’s a long jump, but in terms of existing settings, not a huge amount that should be affected.

First up, part of what ended up being the 1.0.0 release was a conversion of the existing settings to what I’ll call a more stable version. Forgive moments of techy/code-y talk, but basically converting an indexed array to a named array for the CPTUI settings storage. One smart thing I did at the time was not delete the pre-1.0.0 option, in case rollbacks were needed.

You are not quite right in part of your statement above. With that update routine, we do not affect the posts, we do affect the saved option for our settings and create a new setting. Also nitpicky terminology, we don’t create any new tables, just an option row in the wp_options tables. Just clarifying.

As is, the dashes should end up remaining as part of the found settings, but once you go in and try to edit them, there is javascript tied to JUST the slug field to convert them to underscores. The rewrite slugs should remain untouched. If somehow the post type slugs are being converted to underscores as part of the settings updates, then that’s an odd, unintended, case, but also probably the primary source of headache here. I do know there are in fact ways around this and can go into better detail about it, if needed.

That said, it’s good to hear that the content is in fact still in the database like you desired and I expected. Just a matter of getting slug details matched up so that the appropriate custom post types can start getting registered again and the site going forward like everyone hopes.

I can’t promise anything, but I won’t argue against having a copy of your pre-converted option rows just to try with. I know I was testing a lot before the release way back when, and I know majority of our users are above that version by now. However just in case something is found that can be done, I can always touch up the conversion function. Email it to [email protected]