Update to 9.0 made all custom taxonomy disappear

latro666,

I’m willing to do what I can to regain your confidence, but I understand the massive frustrations as well.

I am curious if the issue at hand here is because you corrected things for the version of the settings that were created in either 1.0.0, or 1.0.1, and with 1.0.2 were some changes for how the settings were re-applied, thus re-breaking.

My hope is, with the now 1.0.2 version, that users will be able to go from 0.9.5 straight to 1.0.2, without issue except for a need to refresh permalinks. However, as I’ve seen in the past week, we have people who are stuck in between, thanks to the saved new version of the options in the database. If things are working as they should be, deleting that new version, meaning cptui_post_types and cptui_taxonomies, will trigger a re-conversion from the OLD settings in 0.9.5, and finally work as expected.

If I haven’t completely lost you yet, I’d love it if you could help confirm that being the case.

The reasoning behind the update is that I felt the UI was showing its age, and had barely evolved in the 5+ years it’s been around, while WP Core has evolved. Underneath in the actual code, it felt more difficult to work with than it needed to be, and the code was showing its own age. I hope it’s now going to be much easier for me to continue adding and developing the plugin and more foolproof against other issues.

Two ways for the manual data fix.

—————————-
◆The “post_type” re-checking one by one

Dashboard > CPT UI > Add/Edit Taxonomies

“Edit Taxonomies”tab select a taxonomy to edit.

Check the “post_type” ex)post/page/media
“Edit Taxonomy”

All taxonomies processed repeatedly.

—————————-
◆Add a cord to functions.php file.

Dashboard > CPT UI > Import/Export
“Get Code”tab

Copy the “All CPT UI Taxonomies” area.
Paste localtext.

—–
register_taxonomy( ‘yourTaxonomy’, ”, $args );
—–
↑all these words grep like this↓
—–
register_taxonomy( ‘yourTaxonomy’, array( ‘post’ ), $args );
—–

and copy/paste to functions.php file. Upload.

—————————-

!Caution

Dashboard > CPT UI > Import/Export
“Taxonomies”tab area

“object_types”:[“post”],”object_type”:[“post”] and “post_types”:[“post”] are intermingled by the version.
So I don’t recomend to change this area.
(Is this the cause?)

That last part likely is part of the cause, and the people who were early updaters are sadly in the middle of it. The 1.0.2 release is meant to fix and properly match these up.

Easiest way to hopefully get around this is to just delete the new saved options that were made from the old options, and then let version 1.0.2 re-convert. The “object_types”, plural, is the one that’s needed to be listed.

Is anyone willing to help me test 1.0.3? Specifically anyone that’s already on 1.0.2 and has it working? There are some rewrite rule logic changes that I’m worried about for people who got back to a good place, and I would love to have it confirmed that these changes do not break something again. If you have a dev site that you can try it on, I would appreciate you for forever.

Doing what I can to prevent more issues on a mass scale, if possible. Please let me know and I’ll link you to the appropriate zip file.

Anyone still subscribed to this thread still having issues with the latest version? Or have you been hesitant to try upgrading again? Anything I can do to help get you upgraded finally?

Hey Michael,
I’ve been good with the last couple of upgrades. Thanks for all your help.

Awesome to hear Becky.

Hi all, I was reading this thread a couple of months back but gave up after trying a couple of the fixes to no avail. My live site uses 0.9.5 but when I try to upgrade, even with the “becky fix” of the little plugin you wrote, my taxonomy labels disappear (which form a crucial part of site navigation). Do you have a clear upgrade path for 0.9.5 to 1.x? I feel confused by the back and forth…

It’s been a lot of cases of trying to ensure that the 0.x settings mapped accurately and properly to the 1.x setup. It’s been a long frustrating path, but I think things are in a much better position than they originally were.

That said, I am hoping 1.0.8 is where it needs to be. Worst case scenario, I’d suggest deleting the new settings from the database and let the plugin re-convert the original ones, which I did not overwrite or delete, and see if that helps.

Otherwise, you say it’s an issue with labels? Have you tried setting them manually instead of letting the plugin fall back to default values at all?

More to the point, it’s the singular label that doesn’t show… although the NAME does show. Here’s the code to generate the output:

$output .= '<li class="taxonomy taxonomy-' . $taxonomy->name . '"><h3><a rel="' . $taxonomy->name . '">' . $taxonomy->singular_label . '</a></h3>'

And here’s the actual output…

<li class="taxonomy taxonomy-employment_law"><h3><a rel="employment_law"></a></h3>

As you can see the name works, but the singular label does not, despite the fact that the “Employment Law” taxonomy is indeed linked to posts in the edit taxonomy screen and also has a singular and plural label displayed in the edit taxonomy screen. I’m lost!

Do you have the singular label set in the taxonomy CPTUI editor screen for this taxonomy in question?

Looks like this is a snippet of code/html that’s being output on the frontend.