Classic Editor – How to Get it Back and Remove GutenbergWritten by: zacbanas on September 4, 2019
Not interested in me flexing my writing skills? Here’s a summary of how to disable Gutenberg and Keep the Classic Editor:
Plugins > Add New Plugin > Classic Editor > Install > Activate > Done
Since the release of WordPress 5.0 on December 6th, 2018, there have been a lot of unhappy users. The Gutenberg editor was the biggest change WordPress has had in a long time, and it is not going over well. The Gutenberg editor currently has 4 times as many 1 star reviews as it does 5 stars*. The support team has only resolved 3 out of 48 issues* in the last two months, hinting at even bigger problems.
How to disable Gutenberg and Keep Classic Editor
Getting the Classic Editor back is really simple. What we are going to do is go into your WordPress dashboard and navigate to the Plugins section. At the top of the page, there should be a button that says “Add New”. We are going to click that button.
Enter “Classic Editor” into the search bar, and the following should show up:
We are going to click “Install Now” and after a few seconds, when the button changes color, you are going to click “Activate”. Once that is done, you have officially “removed Gutenberg” and added the old editor back onto your WordPress site. When you go to add a new post or edit an existing one, you should be met with the following screen:
This is the proper way to disable Gutenberg and keep the Classic Editor in WordPress. If have you have any issues doing this, I am more than happy to walk you through the process over a Skype chat.
I am also available for other WordPress related consultations, just shoot me an email at firstname.lastname@example.org and I will get back to you by the end of the day in most cases.
Feel free to also check out some of my other WordPress articles if you’re having a hard time understanding your CMS. Not finding any of my articles useful? Try WPbeginner, they have tons of awesome content and have been doing it way longer than I have.
Thank you for reading!