Bug related to CPT UI plugin taxonomies

Have you been doing any work or customizations with the pre_get_posts action hook at all, to modify queries elsewhere? It’s possible that those are affecting more than intended.

Thanks for your quick response ??

I have not used pre_get_post.

I have used customizations to display post:
https://prnt.sc/y-3IKCRq3GZo

I have several Custom post types, in some it works well and in others it doesn’t:
https://prnt.sc/Vu1YRSXIKYZC

• This reply was modified 2 years, 3 months ago by Alberto.

Attached the debug information of the CPT UI plugin:
https://drive.google.com/file/d/1EhHOLwuzKj8cLNYg9-TMt2rPsYiJjnaQ/view?usp=sharing
Thanks for the help

Something must be altering queries somewhere, as CPTUI itself doesn’t affect them at all.

Not sure if this is on a dev site at the moment or a public one with traffic, but I’m curious if it’d be possible to deactivate other plugins temporarily and check to see if the query listing shows like expected at that time.

I already deactivated the plugins and the theme and it keeps failing.

I can give you access to the same dev site if you wish.

• This reply was modified 2 years, 3 months ago by Alberto.
• This reply was modified 2 years, 3 months ago by Alberto.
• This reply was modified 2 years, 3 months ago by Alberto.
• This reply was modified 2 years, 3 months ago by Alberto.
• This reply was modified 2 years, 3 months ago by Alberto.

Please reach out via https://pluginize.com/contact/ and provide a link to https://www.ads-software.com/support/topic/bug-related-to-cpt-ui-plugin-taxonomies/ in the message, so we know which support thread the request relates to.

Thanks.

thanks, but now there is no support schedule

• This reply was modified 2 years, 3 months ago by Alberto.

Responded privately. Thank you.

Do I give you access to wordpress here?

No. We’ll discuss the issue further in the private correspondence.

Waiting on confirmation from @albert0deavila but the issue looks to have stemmed from both the post type and an associated taxonomy having the exact same slug.

Confirmed that that was the issue.