How to disable the Gutenberg block editor and restore the old WordPress editor

If one of your questions is in the list below then you are in the right place, we will help you get back your old WordPress editor.

  • How do I switch back to the old WordPress editor?
  • How do I change the default WordPress editor?
  • How do I disable classic editor in WordPress?
  • How do I disable Gutenberg editor?
  • How to Disable the Gutenberg WordPress Editor?
  • Is it possible to go back to classic from the new Blocks …
  • Please revert back to the old editor!
  • Unable to switch between Classic Editor and Block Editor …
  • Give me back the old editor!

Did your usual WordPress editor on the website or blog suddenly disappear after upgrading your WordPress version? Here’s how to get it back

This is as a result of a new development called the Gutenberg editor

What is Gutenberg?

“Gutenberg” is the name of the project to create a new editor experience for WordPress with an aim of  creating a new post and page editing experience that makes it easy for anyone to create rich post layouts.

Gutenberg was merged into WordPress 5.0, and officially released on December 6th however it turned out to be the most controversial release in a while, but the usage and adoption metrics are improving!

This was the kickoff goal:

The Gutenberg editor will endeavour to create a new page and post building experience that makes writing rich posts effortless, and has “blocks” to make it easy what today might take shortcodes, custom HTML, or “mystery meat” embed discovery.

Some of the reasons it was created was to allow the:

  • Authoring richly laid-out posts is a key strength of WordPress.
  • By embracing blocks as an interaction paradigm, we can unify multiple different interfaces into one. Instead of learning how to write shortcodes and custom HTML, or pasting URLs to embed media, there’s a common, reliable flow for inserting any kind of content.
  • “Mystery meat” refers to hidden features in software, features that you have to discover. WordPress already supports a large number of blocks and 30+ embeds, so let’s surface them.

How to get back the old Editor

After the upgrade to load the Gutenberg editor by default, many WordPress users have had a problem using the block editor because it was either too cumbersome or the block mechanism was just not cutting it.

WordPress devs probably anticipated it and in place created the Classic Editor plugin to revert the changes that came with the Gutenberg editor.

So just click and install the Classic Editor plugin and you will have your default WordPress editor back. WordPress have commited to supporting and updating Classic Editor until 2022 so it will probably be good to learn how to use the Gutenberg editor.

Wordpress-5-Switch-Back-To-Classic-Editor-old WordPress Editor
WordPress-5-Switch-Back-To-Classic-Editor-old WordPress Editor

What are “blocks” and why is WordPress introducing them?

The current WordPress editor is an open text window—it’s always been a wonderful blank canvas for writing, but when it comes to building posts and pages with images, multimedia, embedded content from social media, polls, and other elements, it required a mix of different approaches that were not always intuitive:

  • Media library/HTML for images, multimedia and approved files.
  • Pasted links for embeds.
  • Shortcodes for specialized assets from plugins.
  • Featured images for the image at the top of a post or page.
  • Excerpts for subheadings.
  • Widgets for content on the side of a page.

All of the above items could be blocks: easy to search and understand, and easy to dynamically shift around the page. The block concept is very powerful, and if designed thoughtfully, can offer an outstanding editing and publishing experience.

So there you have it, you can now get back your original WordPress Editor but only till until 2022

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 152 other subscribers


%d bloggers like this: