How do I try Gutenberg in a safe way, so that I can enjoy the new editor without first breaking my site? If you’re asking yourself this question, you’re not alone. Toolset Types allows you to enable the new Gutenberg editor exactly on the pages that you want and go back to the classic editor if you run into problems.
We added this new feature to Types 3.2.2 because we wanted to see how Gutenberg is working on our own sites. Of course, we only update to WordPress 5.0 on development sites, but that is still a problem. Our sites use many plugins and run a lot of custom code. So, there’s a lot that can go wrong with a completely new editing interface.
We want to try the new Gutenberg editor on our production sites gradually. First, we’ll enable Gutenberg to edit *new blog posts*. When we see that it’s all good, we’ll switch it over to editing *old blog posts*. Then, we’ll try it for *new pages* and so on. We use many other “post types” on our sites and we’ll try Gutenberg on each of them separately. This way, we know that we’re not breaking anything and that nothing is missing.
I’m pretty sure that as we go through this upgrade, we’ll run into plenty of issues and deal with them. The good thing is that we’ll know that nothing is broken without us handling it. If we switch over the entire site, we can expect chaos for the next few weeks, which we’d rather avoid.
Enabling Gutenberg per post type
So, we came up with the new “Editor” column in the Toolset Dashboard.
This column allows to choose the default editing mode for each post type.
Alternatively, you can select the post editor when editing a post type on the Toolset -> Post Types page.
Controlling Gutenberg per page
When we edit individual pages (posts, CPTs), we also get new Switch to the Block Editor buttons. If you’ve used page builders in the past, these buttons will look very intuitive to you. You will be able to enable or disable Gutenberg for individual content.
Once you’ve enabled Gutenberg, if you’re not happy with the results, you can always go back to editing with the Classic Editor.
When switching from the Classic Editor to Gutenberg (Block Editor), Toolset makes a copy of your content. This allows Toolset to restore your content to exactly what it was if you’re switching back to the classic editor.
A safer update path to WordPress 5.x
We hope that this will give us all a safer and saner path to updating WordPress. We can postpone the WordPress 5.0 update a bit, but not indefinitely. When we update, we want to know that our sites continue working correctly on the front-end and when editing.
We want to know what you think, if you have questions and ideas. Please leave your comments here and we’ll get back to you.