On December 6, 2018 the update to WordPress 5 was released, which makes Gutenberg the new standard editor. If your WordPress site is not yet compatible with Gutenberg or you are currently rejecting the new editor for other reasons, this is no reason to despair. Because fortunately there are some ways to avoid the Gutenberg-editor – or at least delay the implementation for the time being.
The major update to WordPress 5 which integrates the Gutenbergeditor into the WP core was released surprisingly in December 2018. The reactions to Matt Mullenwegs late notice - 3 days before the new release date - are anything but positive.
Since there is still quite a few open tickets gives, demand WordPress -users already for several weeks, the publication of WordPress 5 to be postponed to January. In addition, there WordPress are some uncertainties regarding compatibility and a release in the pre-Christmas period is therefore criticized for two reasons:
- The Christmas business is the most important time of the year for many shop operators. Postponing the release until January would give them more time to test, and any problems encountered would have less serious consequences.
- It is to be expected that web designers, Plugin- and Theme-developers, hosters and Co. after the release there will be an increased support effort. This is also conceivably unfavorable during the Christmas season.
If you haven't Gutenbergdone your homework yet, you might want to take a look at our Gutenberg-Article and our e-book "WordPress 5 & Gutenberg- Update or wait and see?" to get your own impression of the new WordPress -editor.
Due to the uncertainties surrounding the update to WordPress 5 many people ask themselves WordPress -User the question: "How can I avoid the Gutenberg-editor?".
In fact, there are several ways to use the new WordPress -editor or (for the time being) bypass it completely. So that you can make the change to WordPress 5 at your own pace, I would like to introduce you to some of these possibilities:
If, before updating to WordPress 5, you change the Plugin"Classic Editor"the Gutenbergeditor will be automatically suppressed in the new version.
The "Classic Editor"-Plugin has two modes:
- Either it completely suppresses the Gutenberg-editor and restores the interface of the classic editor.
- Or it inserts links in the Admin menu, so you can choose for individual posts or sites the classic editor (just as you currently choose between Gutenberg and Classic, if the Gutenberg- isPlugin active).
With over 600,000 active installations the "Classic Editor" plugin is the most common method to suppress the Gutenberg editor. This is not a surprise because since WordPress 4.9.8 this plugin is officially recommended in the WP-Admin dashboard by the Gutenberg core team.
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 shall, at least until 31 December 2021 officially supported byWordPress.
Since the update to 4WordPress .9.8, WP users get a prompt in the admin dashboard to test the Gutenberg-editor. If you are concerned that this message is unnecessarily unsettling your customers, you can send this notification with the Plugin"Dismiss GutenbergNag" fade out.
Another WordPress plugin with which you can avoid the Gutenberg editor is "Disable Gutenberg”. This Pluginhas been wordpress.orgdownloaded almost 35,000 times and is sites active on over 10,000.
In the default setting of the "Disable Gutenberg"-Plugins will the Gutenberg-editor for all users of your WordPress site deactivated. You also have the option of deactivating the new WP Editor only for certain user roles or content types.
Recently you have been able to Gutenberg with which, Pluginamong other things, you can deactivate for Themetemplates and for certainsites contributions/IDs, as well as the "Test Gutenberg"-Remove message in admin dashboard.
The Plugin"Gutenberg Ramp"was developed by Automattic - the company behind wordpress.comit. In principle, it offers similar functions to "Disable Gutenberg", but is less beginner-friendly, as it cannot be operated by simple checkboxes in the Pluginsettings.
Firstly, "Gutenberg Ramp" restores the classic editor. On the other hand, you can use the function Gutenberg_ramp_load_gutenberg() determine in which cases the Gutenbergload should be done (e.g. always; never; only for certain Post IDs, Post Types, sites etc.).
The "easiest" way to avoid the Gutenberg-editor is to not update to WordPress 5 at first. For example, there RAIDBOXES is the possibility to change the Fix WP version and thus to automatically sit out all major updates. However, this is not a permanent solution, as we only support the three latest major WordPress versions for security reasons.
Even if it's several ways If there is any way to get around the new editor, we would like to encourage you, Gutenberg to give you a fair chance. Because basically we are of the opinion that the Gutenberg-editor has great potential and will bring it forward in the WordPress long term.
At RAIDBOXES WordPress 5 we will make them available for testing and early adopters after the release. But we will do the automatic update later than usual. Normally we play Major Updates already 14 days after release. At WordPress 5 we will wait until the most important Pluginsones have been tested Themessufficiently on the new version. If you don't want to switch to WordPress 5 in the near future, remember to change RAIDBOXES your WordPress -Version to fix.
With this solution, early adopters and curious webmasters can quickly use and test the new WordPress version without endangering the stability of their customer sites.
Do you want to talk about WordPress 5, the Gutenberg-Editor and other topics around WordPress exchange? Then look directly in our RAIDBOXES Slack -Community For WordPress professionals!