In the waning days of 2018, WordPress unveiled the new post and page editor named Gutenberg and the world rejoiced. And by “rejoiced,” I mean they almost universally heaped condemnation and hatred upon the defenseless new editor. Users were accustomed to what became known as the “classic editor” in WordPress, and the modern new block editor left many scratching their heads in confusion.
But that’s human nature, isn’t it? It doesn’t matter if a change is an improvement, we just don’t like the change of any kind. Henry Ford was supposed to have said, “If I had asked people what they wanted, they would have said a faster horse.” Meaning they didn’t want cars. They couldn’t see the future the way Henry could.
Well, Ford wasn’t a barrel of laughs, so it’s probably not surprising that he didn’t actually make that crack about faster horses. But the point remains, most of us generally don’t like change. The Gutenberg editor is a major change, and it’s there by default any time you install WordPress.
1. The Problem With Gutenberg
The pre-Gutenberg editor had been around for a long, long time. Many WordPress plugins were developed to extend its functionality and customize its operation. And if you think about working in the admin panel of WordPress, creating a new post or page, you aren’t usually in there just larking about. You have a job to do and you want to get in, do the job, and get out.
That’s not possible when the major tool that you use to do the job has been thrown out and replaced with a strange new device that has you doing Google searches just to learn how to add an image to a post.
The benevolent contributors to WordPress heard the anguished cries of the people and released a plugin imaginatively named “Classic Editor.” And in a short amount of time, millions of WordPress users had it installed.
Let’s join them and install it ourselves, I’ll show you how to do it.
2. Installing the WordPress Classic Editor
Log in to your WordPress admin panel.
In the left column navigation mouse over the “Plugins” link and click the “Add New” link.
In the “Search plugins…” box, enter “Classic Editor.”
Once you have located the plugin, click the “Install Now” button.
When the plugin has been installed, click the “Activate” button.
3. Configuring the Classic Editor
Well, actually, there is no configuration. Once the plugin is activated, Guttenberg is gone.
But it’s not really gone.
You can still use the Gutenberg editor if you want to, for a specific page or post, or just to learn how it works. Here’s how to access it.
In the left column navigation, mouse over the “Settings” link and click the “Writing” link.
In the “Allow users to switch editors” section, select the “Yes” radio button.
Scroll down and click the “Save Changes” button.
Now when you start a new post or page, on the right side you’ll see an “Editor” section.
When you click the “Switch to Block Editor” link, you’ll be taken to the Gutenberg editor.
4. Switching Between Editors While Writing a Post
If you’re in the Gutenberg editor and want to switch back to the classic editor, you can do that.
If you are in the middle of a post, save it before switching editors! Post content is not saved when the editors are switched.
Click the ellipses in the main Block Editor menu.
And click the “Switch to Classic Editor” link.
5. Back to the Future
It has to be difficult, if you look at it from the WordPress corporate perspective, to spend years developing something that you think is great and then have most of your users hate it.
I saw the father of WordPress, Matt Mullenweg, give an early demo of Gutenberg at a conference five years before it was released, so it wasn’ something they threw together overnight or bought from a developer on the dark web.
WordPress could have forced everyone to use Gutenberg, but they no doubt knew that independent plugin developers would introduce their own plugins to disable the Gutenberg editor (which they quickly did), so they bit the bullet and came up with the official Classic Editor plugin for WordPress.
You have to give them credit for that. But the fact that there are over five million active installs of Classic Editor pretty much tells the tale (the active installation count only goes up to five million, so the actual number is likely much higher).
6. But Is It Really That Bad?
If you look at the editor in WordPress objectively, as a tool, the Gutenberg block editor is a major improvement over the tired old TinyMCE “classic” editor.
The Gutenberg editor is more of a design tool, and maybe that’s where a lot of WordPress old-timers lose the thread. They’re used to the design part of WordPress being much more difficult, and they miss those days.
Have you taken the time to learn how to use the Gutenberg editor? If you still use the “classic” editor, do you have any plans to eventually switch to the block editor?