If you updated to WordPress 5.0 and have decided that the new editor (GUTENBERG) is just not for you..there is an easy way to go back to the classic editor or the editor your theme uses (WP Page Builder and others)…it is a plugin named “Disable Gutenberg”. Here is a little about the plugin (via WordPress):

This plugin disables the new Gutenberg Editor (aka Block Editor) and replaces it with the Classic Editor. You can disable Gutenberg completely, or selectively disable for posts, pages, roles, post types, and theme templates. Plus you can hide the Gutenberg nag, menu item, and more!

The all-in-one, COMPLETE solution for handling Gutenberg.
Hide ALL traces of Gutenberg and replace with the Classic Editor.
Restores the original Edit Post screen (TinyMCE, meta boxes, et al).

The Disable Gutenberg plugin restores the classic (original) WordPress editor and the “Edit Post” screen. So you can continue using plugins and theme functions that extend the Classic Editor. Supports awesome features like Meta Boxes, Quicktags, Custom Fields, and everything else the Classic Editor can do.

Does not “expire” in 2022! 🙂

Easy to Use

Just activate and done! The default plugin settings are configured to hide all traces of the Gutenberg Block Editor, and fully restore the original Classic Editor. Further options for customizing when/where Gutenberg is enabled are available in the plugin settings.

Click here to learn more about this plugin:   https://wordpress.org/plugins/disable-gutenberg/

It really is that easy…just load and activate the plugin and you are all set and back to the environment you had before the upgrade.

Hope this is helpful to the WordPress users reading the blog.

Scott E

1 COMMENT

  1. In terms of will not expire in 2022, a little more clarity is required. Contrary to general understanding, the the workings of the original editor has not been removed from WordPress, it is just subject to a REACT override that enables Gutenberg. All methods of disabling the new block editor and presenting the classic editor are just a a switch, albeit a sophisticated switch in the case of some plugins using conditional configuration.

    We are informed that by 2022, the classic editor functionality will be removed from WordPress core. In this event third party developers will need to engineer their plugins to include the workings of the old editor. Wether this engineering will be reliable is a big question open to debate in the future.

    I am not making apologies here for the new editor but the writing is on the wall for having to ultimately having to adopt it. To this end it’s a pity that it, Gutenberg itself, wasn’t engineered better, taking into account all the workflows that are possible with the older editor.

LEAVE A REPLY

Please enter your comment!
Please enter your name here