Closed bobbingwide closed 2 years ago
Enable a Custom Post Type's registration to be changed to either support show_in_rest
or not.
This can be used to control, by post type, which editor gets used.
show_in_rest | Default Editor | Other editor |
---|---|---|
Checked | New Visual / Code editor | Classic Visual / Text editor |
Unchecked | Classic Visual / Text editor | none |
This applies to custom taxonomies as well.
The show_in_rest
option is a useful field to display in the post type list. We can consider combining the information gathered for the [content]
shortcode, being developed for oik-block, into the summary displays for oik-types.
Note: If the post type has show_in_rest
true but custom taxonomies are show_in_rest
false then
Gutenberg will not display the custom taxonomies. It gets a 403 error. This is a backwards compatibility problem.
There is another situation where Gutenberg crashes when trying to load the custom taxonomies, due to a 404 being returned on the REST request. I don't know if this has been raised as a Gutenberg issue. It's not that easily repeatable.
Delivered in oik-types v2.0.0-alpha-20181019
Since early 2017 a new editor has been under development. Code named Gutenberg this new editor is being developed as a feature plugin. It is expected to be merged into core for WordPress 5.0.
We need to be aware of Gutenberg and to attempt to be compatible with it. Actually, it's the other way round. Gutenberg needs to be backward compatible with us.
show_in_rest