On December 6, 2018, the update to WordPress 5 was released, making Gutenberg the default editor. If your WordPress site is not yet compatible with Gutenberg or you currently reject the new editor for other reasons, this is not yet a reason to despair. Fortunately, there are a few ways to get the Gutenberg-Editor or at least delay it for the time being.
The major update to WordPress 5 which integrates the Gutenberg editor into WP core was surprisingly released in December 2018. The reactions to Matt Mullenweg's short notice announcement - 3 days before the new release date - are anything but positive.
Since there are still quite a few open tickets WordPress users have been asking for the release of WordPress 5 to be postponed to January for several weeks. into January. In addition, WordPress 5 brings some uncertainties in terms of compatibility with it and a release in the pre-Christmas period is therefore criticized for two reasons:
- Christmas is the most important time of the year for many shop owners. Postponing the release until January would give them more time for testing and any problems that occur would have less serious consequences.
- It is to be expected that web designers, Plugin- and Theme- developers, hosters and Co. will have an increased support effort after the release. This is also very unfavorable during the Christmas season.
If you haven't yet had a chance to explore Gutenberg , it's best to start by checking out our Gutenberg article and our e-book "WordPress 5 & Gutenberg - Update or wait?" to get your own impression of the new WordPress editor.
Due to the uncertainties surrounding the update to WordPress 5, many WordPress users are asking the question, "How can I avoid the Gutenberg editor?"
In fact, there are several ways to disable or completely bypass the new WordPress editor (for now). To help you make the switch to WordPress 5 at your own pace, I'd like to share some of these options with you:
WordPress If you have downloaded the Plugin "Classic Editor"before updating to Gutenberg 5, the editor will be automatically suppressed in the new version.
The "Classic Editor" -Plugin has two modes:
- Either it suppresses the Gutenberg editor completely and restores the interface of the classic editor.
- Or it adds links in the admin menu so you can select the classic editor for individual posts or sites (like you can currently switch between Gutenberg and Classic when the Gutenberg-Plugin is active).
With over 600,000 active installations the "Classic Editor" -Plugin is the most widely used method to suppress the Gutenberg editor. This is no surprise, as the Plugin is officially recommended in the WP admin dashboard by the Gutenberg core team since WordPress 4.9.8.
Until when the Plugin would work, however, was unclear for a long time. But since November 7, the uncertainty has come to an end: The "Classic Editor" -Plugin is officially supported by WordPress at least until December 31, 2021.
Since the update to WordPress 4.9.8, WP users get a prompt in the admin dashboard to test the Gutenberg editor. If you're concerned that this message will unnecessarily alienate your customers, you can disable this notification, for example, with the Plugin "Dismiss Gutenberg Nag" hide.
Another WordPress -Plugin, with which you can avoid the Gutenberg-Editor, is "Disable Gutenberg”. The Plugin has been downloaded almost 35,000 times from WordPress .org and is active on over 10,000 sites .
The default setting of "Disable Gutenberg"-Plugins disables the Gutenberg editor for all users of your WordPress site disabled. In addition, you have the option to disable the new WP editor only for specific user roles or content types.
Recently, you can disable Gutenberg with the Plugin for Theme templates and for certain post/sites IDs, among others, as well as remove the "Test Gutenberg" message in the admin dashboard.
The Plugin "Gutenberg Ramp" was developed by Automattic - the company behind WordPress .com - developed. It basically offers similar features as "Disable Gutenberg", but is less beginner-friendly, as it is not operated by simple checkboxes in the Plugin settings.
On the one hand, "Gutenberg Ramp" restores the classic editor. On the other hand, you can use the function gutenberg_ramp_load_gutenberg() to determine in which cases Gutenberg should be loaded (e.g. always; never; only for certain post IDs, post types, sites etc.).
The "easiest" way to bypass the Gutenberg editor is not to update to WordPress 5. At RAIDBOXES , for example, there is the possibility to fix the WP version with one click. WP version with one click and thus all major updates will be automatically suspended. However, this is not a permanent solution, as we only support the three most recent major WordPress versions for security reasons.
Also, if there are some ways to bypass the new editor, we encourage you to give Gutenberg a fair chance. Basically, we think that the Gutenberg editor has great potential and will bring WordPress forward in the long run.
At RAIDBOXES we will make WordPress 5 available for testing and early adopters after release. However, we will do the automatic update later than usual. Normally we play major updates 14 days after release. For WordPress 5, we will wait until the major Plugins and Themes have been sufficiently tested on the new version. If you don't want to switch to WordPress 5 in the near future, remember to fix your RAIDBOXES dashboard to your WordPress version in your dashboard.
With this solution, early adopters and curious webmasters can quickly use and test the new WordPress version without jeopardizing the stability of their client sites.
Would you like to talk about WordPress 5, the Gutenberg editor and other topics related to WordPress ? Then take a look at our RAIDBOXES Slack community for WP professionals!