CPT not showing custom taxonomies

Is it gutenberg blocks that are creating all of the output for these? or is the more traditional template-level route that’s showing output for the associated terms?

If the template level, chances are you will need to edit the templates in question to check for your custom taxonomies. As is, it looks like it just checks for category

Something like https://developer.www.ads-software.com/reference/functions/get_the_term_list/ would be useful here.

If it’s Gutenberg blocks that are controlling output, then I think that’s a fairly new thing with WordPress in general, and block settings may need reviewed to confirm that they will even show custom taxonomies.

We’ll actually in the block settings I selected my custom taxonomy, but they don’t appear in the loop on the backend. Then the WordPress ones appear on the frontend.

And the block is controlling the output.

So, I created the CPT and the taxonomy. Then I assigned the taxonomy to the CPT and in the CPT I assigned compatibility with the custom taxonomy and not with the WordPress ones.

Is that all I need to do in CPT UI settings?

• This reply was modified 2 years, 10 months ago by GWKaplan.

Honestly sounding like the block isn’t as robust as needed for your intended use case here. CPTUI only handles the registration of the content types, and then “duck” into the back of things, out of the way.

We don’t have any settings that dictate how blocks behave or settings within them, as well as no direct influence on templates either.

So it’s nothing that you’ve done wrong or anything, in this case.

Ok, thanks!

Welcome.