Custom Taxonomy: Show in REST, Hide default Gutenberg Panel

[spwarner]

I’ve created a custom taxonomy for my custom post type, but I have built a custom interface for assigning the tax (a drop-down as I want only max 1 term assigned) as part of a metabox for the CPT. I want to show the taxonomy in the Admin UI so it’s easy to add/edit terms, but I want to hide the default chooser panel for the tax on the custom post type. In the classic editor, setting ‘meta_box_cb’ => false does the trick, is there any similar way to do this in Gutenberg? I want to show the taxonomy in REST so I can build my custom selector functionality so I set ‘show_in_rest’ => true, but then I get the default chooser in Gutenberg too (in its own panel under Document in the Inspector). How can I remove this - it would be good to have a filter or attribute that can be set to remove the default tax chooser.

[danielbachhuber]

Hi @spwarner,

You can use show_ui=false to disable the Gutenberg UI, see https://github.com/WordPress/gutenberg/blob/master/editor/components/post-taxonomies/index.js#L21

[spwarner]

Yes, but then it removes the tax management interface as well (which I want to keep). Is there any way to keep the admin interface to manage the tax, but hide the default tax chooser in Gutenberg? Here's the screenshot of the admin interface that I want to keep, but gets removed with show_ui=false:

[danielbachhuber]

Is there any way to keep the admin interface to manage the tax, but hide the default tax chooser in Gutenberg?

I don't have a good answer to this at the moment. We'll work something out in the near future. I've filed this against the Merge Proposal: Back Compat milestone so it has visibility.

[spwarner]

That'll do for now, thanks! I'd just like to have this functionality when 5.0 ships.

[Ipstenu]

It’s not uncommon for people to use taxonomies to extend custom meta boxes in cmb2 or acf. In doing so, they intend to limit the use of the taxonomy (such as make it a drop down to prevent people from adding to it in situ). While much of this will be adapted to Gutenberg blocks and templates, as it should, it will still be important to hide them from post content.