Still issues with 1.0.2

Hi darkhorse20,

My apologies that you’re going through this, I am willing to help as much as I can to figure it out. My first goal here is to get the registering/functionality back to what’s expected.

To clarify, are the taxonomies not showing up at all for the post types, including being listed as a submenu item? Is this so even with doing some quick editing to re-associate via each taxonomy edit screen? Or is it a case of they’re associated, but the checkbox isn’t being checked properly when you go to edit a taxonomy.

Did you go from 0.8.5 directly to 1.0.2? or did you go from 1.0.0 or 1.0.1 to 1.0.2? Trying to isolate possible areas where an issue could stem from.

Regarding the UI, it’s something I can keep working on and improve over time, and I would appreciate any feedback you have on it so that I can help make it better for everyone.

Hello,

Sorry about my rant, your plugin is really great. This last major update has just been a nightmare for me.

The taxonomies are not showing up in the submenu of the custom post type but they are showing up as taxonomies in the taxonomies section. However, they are not associated with any custom post types.

This has happened upgrading from 0.8.5 to 1.0.2 .

I don’t know if anyone has brought this up yet but I’ve noticed this happened a couple times on custom post types that are non-public with a taxonomy. A custom post type can only be assigned a taxonomy if it is public. But after the taxonomy has been added, the custom post type can be changed to non-public and still function the same.

Do you think that has anything to do with it?

I understand the frustration, and I’ve been along for everyone’s issues, so I know how it feels vicariously. It’s been an interesting month.

Interesting, and an edge case that I didn’t envision at all. Help me mentally work this out, with regards to where the issue is coming from. Is it because the post type is set to non-public after the association?

I know that for the taxonomy edit screen, I have the following filter that is part of the get_post_types() function usage.

$args = apply_filters( 'cptui_attach_post_types_to_taxonomy', array( 'public' => true ) );

...

$output = 'objects';
$post_types = get_post_types( $args, $output );

If needed you could change the arguments used to include all post types https://codex.www.ads-software.com/Function_Reference/get_post_types.

Not sure if this is going to help this specific case, but it’s available to use.

Let me know if I’m way off base with anything, I’m all ears for how to get this into a working situation.

I ended up having to update around 40 websites manually because of the plugin. After every update, if the CPT was broken after the plugin update, re-saving the permalinks fixed it.

Thank you for the feedback. I may go ahead and release 1.0.3 next week which I’m hoping will have some fixes that reduce need to re-save permalinks. I didn’t do it this week because I wanted some feedback that 1.0.3 wasn’t going to wreck already fixed installs.