Pods 2.7.10 Release: Gutenberg and WP 5.0 Compatibility
We are releasing Pods 2.7.10 onto the WordPress.org plugin repository today to accommodate WordPress 5.0 and Gutenberg Compatibility.
Updated Post for 2.7.11 Update: 2.7.11 was also released into the repository to handle an overaggressive Gutenberg Block Editor check. This was causing some conflicts with Classic Editor and Yoast SEO, but has been corrected. If you update to 2.7.11, you should not see any issues.
How to enable/disable Gutenberg in Pods:
- To Enable: You can use the Gutenberg Block Editor on Custom Post Types that have REST API enabled and the ‘Editor’ activated. (Editor is on by default, but may have been turned off under Advanced Options, Supports). Custom Taxonomy that is associated with the post type also need to have REST API enabled if you want them visible in the Block Editor.
- To Disable: Make sure REST API is not enabled on your Custom Post Type that you don’t want to use the Gutenberg Block editor on. If you need REST API but still want to disable Gutenberg, you can use the Classic Editor plugin to disable Gutenberg on your entire site or you can use Gutenberg Ramp to disable on a post-type by post-type basis. If you want to hide Taxonomy from the Block Editor, you will also need to disable REST API on any Custom Taxonomy created with Pods.
What currently IS supported for Gutenberg Compatibility:
- Our “More Fields” meta box will display at the bottom of the screen. All of our field types work normally as before on post types with the Gutenberg Block Editor enabled.
- Auto Templates configured to run on Single & Archives will still show where the_content filter is output.
- Existing Pods Shortcodes within the block editor will still output (and can be edited manually). If you currently have shortcodes in the ‘editor’ in a WordPress page (or in the post editor of a custom post type), when that post type is converted to the block editor, they will be in a ‘Classic Editor’ block.
- New Pods Shortcodes entered within the Gutenberg editor for new/existing posts will continue to function as before, with the caveat listed below about the Pods shortcode wizard not showing.
What currently is not supported by us in Gutenberg (yet):
- Shortcode wizard in the Gutenberg/Block editor. You can still use shortcodes in the block editor, but you won’t have the Pods Shortcode wizard to help you build them. We are actively developing our Gutenberg blocks and will be communicating when it’s ready for testing and subsequent release.
What We Recommend Before Updating:
Install the Classic Editor and Activate it. It is one of the easiest ways to control whether Gutenberg is enabled or active on your site at all. If you need more granular control, we recommend the Gutenberg Ramp plugin. With Gutenberg Ramp, you can selectively activate Gutenberg block editor on a post-type basis (or alternatively with code). It will also recognize which post-types are ‘Gutenberg’ capable, which for Pods means the REST API is enabled on those post-types.
The settings for both of these plugins is within the Admin, under Settings, Writing. Classic Editor settings are at the top of the screen:
Basically, if you don’t want Gutenberg on this site and you’re upgrading to WordPress 5.0, check the option “Replace the Block editor with the Classic editor”. Otherwise, check the option to ‘Use the Block editor by default”. This allows you to use the Gutenberg editor on post-types that support it by default (Pages & Posts) and skip it on those where you don’t have REST API enabled or where you have disabled the ‘editor’ for a post-type under Advanced Options, Supports.
The settings for Gutenberg Ramp are at the bottom of the Settings, Writing screen:
Specifically, if you want to control which post-types are Enabled for Gutenberg, you can select them from the list. Only post-types with the REST API enabled will show in this list. Post-types where you have disabled the ‘editor’ under Advanced Options, Supports, will also not show on this list.
Enabling REST API in your Pods
In order to use the Gutenberg block editor on your Custom Post Types created with Pods, you would need to Enable REST API support. You will also need to take this step with any Custom Taxonomy that you’ve created with Pods and that you want to be accessible within the Block Editor.
You can access REST API settings under the Pods Admin, Edit Pods. From this screen, select the REST API tab and check the box for “Enable”. This is the only setting that is required to make your post-types and taxonomy compatible with the Gutenberg block editor.