How to disable Gutenberg and keep the Classic Editor

In the ever-evolving world of WordPress, change is inevitable. One of the most significant changes in recent years was the introduction of the Gutenberg editor, also known as the Block Editor. While this new WordPress editor brought a modern and dynamic approach to content creation, not everyone embraced it with open arms. If you’ve found yourself in the camp of WordPress users who prefer the Classic Editor, you will want to disable Gutenberg.

A Decision to Disable Gutenberg

I wrote an article back in May 2023, titled “Is the Block Editor Really What People Want“. I touched base on whether the block editor is truly aligned with the needs and preferences of WordPress users. Today, I’m going a step further. This article is dedicated to those who have made up their minds—to disable Gutenberg and stick with the Classic Editor. I’ll guide you through the process, step-by-step, ensuring that you can comfortably continue creating content the way you’ve always known and loved.

But first, let’s take a moment to briefly revisit the pros and cons of both editors and then we will bid adieu to Gutenberg.

Understanding Gutenberg and the Classic Editor

WordPress has always been known for its flexibility, allowing users to choose the tools that best suit their needs. At the core of your content creation experience are two WordPress editors: Gutenberg and Classic Editor.

What is Gutenberg, and why was it introduced?

Gutenberg, also known as the Block Editor, was introduced to WordPress back in December 2018 with version 5.0 as a way to modernize content creation. It takes a block-based approach, breaking content into distinct sections (or blocks) that can be easily manipulated. This approach can be advantageous for users who want to create pages that are more detailed with a variety of content elements. A good example is the Rough Pixels website because it’s completely built with the block editor.

What is the Classic Editor, and its history?

On the flip side, the Classic Editor is a familiar and straightforward tool that has been part of WordPress since the beginning. It offers a traditional, “what you see is what you get” (WYSIWYG) editing experience. If you’ve been using WordPress for a while, chances are you’re well-acquainted with its simplicity and ease of use. Actually, a little side-thought here, it wasn’t perfect either.

Now, let’s delve into the pros and cons of both the Block Editor and the Classic Editor while keeping in mind the keywords you provided.

Pros and Cons of Gutenberg:

Pros:

1. Enhanced Flexibility: Gutenberg’s block-based system allows for creative content layouts, making it easier to design dynamic pages.
2. Rich Media Integration: It seamlessly integrates with multimedia elements, such as images, videos, and embeds.
3. Regular Updates: Gutenberg receives continuous improvements and updates from the WordPress team.

Cons:

1. Steep Learning Curve: The block-based approach can be intimidating for beginners, requiring time to grasp.
2. Compatibility Challenges: Some themes and plugins may not fully support Gutenberg, causing compatibility issues.
3. Complexity for Simple Tasks: Performing basic tasks can feel cumbersome due to the block structure.

Now, let’s examine the Classic Editor’s pros and cons:

Pros and Cons of the Classic Editor:

Pros:

1. Simplicity: It offers a straightforward, WYSIWYG interface that’s easy to understand for beginners and experienced users alike.
2. Stability: The Classic Editor has been a staple of WordPress for years, and it’s widely compatible with themes and plugins.
3. Efficiency: For users who primarily focus on text content, the Classic Editor streamlines the writing process.

Cons:

1. Limited Layout Control: Creating intricate page layouts can be challenging compared to Gutenberg.
2. Less Multimedia Integration: While it supports multimedia, it may not handle rich media as seamlessly as Gutenberg.
3. Static in a Dynamic World: In an era of evolving web design trends, the Classic Editor may seem outdated to some.

In the following sections, we’ll explore the reasons why you might want to consider disabling Gutenberg and opting for the Classic Editor.

Reasons to Consider Disabling Gutenberg

Gutenberg undoubtedly brings innovation to the WordPress and WordPress editor ecosystem, but it’s not a one-size-fits-all solution. There are several reasons why you might want to disable Gutenberg and stick with the Classic Editor:

1. Personal Preferences: Your familiarity with the Classic Editor might make it your preferred choice. If you’re comfortable with a tool that has served you well over the years, there’s no need to switch.
2. Compatibility Issues with Themes and Plugins: Some themes and plugins are not fully compatible with Gutenberg. If your website heavily relies on specific themes or plugins that haven’t yet adapted to the Block Editor, sticking with the Classic Editor can save you from potential headaches.
3. Client or User Preferences: If you’re managing a website for clients or multiple users, it’s essential to consider “their” preferences. Some clients or team members may prefer the familiar interface of the Classic Editor, making it a better choice for collaborative projects.
4. Familiarity with the Classic Editor: If you’re accustomed to the Classic Editor’s workflow and have mastered its features, transitioning to Gutenberg might disrupt your productivity. Staying with what you know can keep your content creation process efficient.
5. Learning Curve: You are busy and simply do not have the time to learn an extensive change; in this case, the block editor. Despite what the WordPress team says, Gutenberg has a steep learning curve for the average end-user.

Now that I’ve taken you through a brief history and the pros and cons of Gutenberg and the Classic Editor, it’s time for me to take you through the step-by-step process of disabling Gutenberg and making the Classic Editor your default choice.

Installing and Activating the Classic Editor Plugin

If you’ve made it this far, you probably have decided to embrace the Classic Editor and disable Gutenberg, WordPress makes it relatively straightforward with the Classic Editor plugin. Here’s a step-by-step guide on how to install and activate it:

Step 1: Log into your WordPress dashboard:

You will need to log into your WordPress admin panel.

Step 2: Navigate to the Plugins Page

Once you’re logged in, look for the “Plugins” tab in the left-hand menu. Click on it to access the Plugins page.

Step 3: Search for the Classic Editor Plugin

On the Plugins page, you’ll see an option to add a new plugin. Click on the Add New button. In the search bar, type “Classic Editor“.

Step 4: Install the Classic Editor Plugin

You should see the Classic Editor plugin in the search results. Click the Install Now button next to it.

Step 5: Activating the Plugin

After the installation is complete, the Install Now button will change to Activate. Click the Activate button to enable the Classic Editor plugin.

Step 6: Adjusting Plugin Settings

With the Classic Editor plugin activated, you can fine-tune its settings. To do this, navigate to Settings > Writing. You’ll find the options to configure the default editor for all users and the default editor for individual users.

Step 7: Save Changes

Don’t forget to save your changes after selecting the Classic Editor as your default. You may need to scroll down and click the Save Changes button at the bottom of the page.

Installing the “Disable Gutenberg” Plugin

If you’re looking for a comprehensive solution to completely disable Gutenberg and keep the Classic Editor as the default editor, the “Disable Gutenberg” plugin by Jeff Starr is an excellent choice.

NOTE: When you install this plugin, you don’t need the Classic Editor plugin because this one will restore it for you. You also have the option to restore the classic widgets screen too.

Here’s a step-by-step guide on how to install and activate it:

Step 1: Accessing Your WordPress Dashboard

Just like the previous steps to install the Classic Editor plugin, you will need to log into your WordPress admin panel.

Step 2: Navigate to the Plugins Page

Once you’re logged in, look for the “Plugins” tab in the left-hand menu. Click on it to access the Plugins page.

Step 3: Search for the Disable Gutenberg Plugin

On the Plugins page, you’ll see an option to add a new plugin. Click on the Add New button. In the search bar, type “Disable Gutenberg“.

Step 4: Install the Disable Gutenberg Plugin

You should see the Disable Gutenberg plugin in the search results. Click the Install Now button next to it.

Step 5: Activating the Disable Gutenberg Plugin

After the installation is complete, the Install Now button will change to Activate. Click the Activate button to enable the Classic Editor plugin.

Step 6: Configuring Additional Settings

The Disable Gutenberg plugin provides further configuration options if needed. To access these settings, go to Settings > Disable Gutenberg. From here, you can customize the settings to your preferences.

You should see this screen/page and then to access more options, click on the Click Here text link. From here, you can fine-tune your options.

By installing and activating the Disable Gutenberg plugin, you’ve successfully disabled Gutenberg entirely, ensuring that the Classic Editor remains the default editor on your WordPress site.

Step 7: Testing and Verifying the Changes

After you’ve installed and activated the Disable Gutenberg plugin or configured the Classic Editor plugin, it’s essential to test and confirm that Gutenberg is disabled, and the Classic Editor is functioning as expected. Here’s how you can do it:

By following these steps and confirming that your WordPress editor is now the Classic one.

Troubleshooting Common Issues

While disabling Gutenberg and embracing the Classic Editor is a straightforward process, you may encounter some common issues along the way. Here are potential challenges and how to troubleshoot them:

1. Gutenberg Remains Active: If, after installing the Disable Gutenberg plugin or configuring the Classic Editor, you still see the Gutenberg editor interface when creating or editing posts, follow these steps:
   • Double-check that the Disable Gutenberg plugin is active. In the WordPress dashboard, go to “Plugins” and ensure that it’s listed and activated.
   • If you’re using a caching plugin, clear your cache to ensure that your changes take effect immediately.
   • Review the Disable Gutenberg plugin settings to confirm that you’ve configured it correctly. Ensure you’ve saved any changes made in the settings.
2. Compatibility Issues with Other Plugins or Themes: In some cases, disabling Gutenberg may cause compatibility issues with other plugins or themes that rely on it. Here’s how to address this:
   • Update your plugins and themes to their latest versions. Developers often release updates to ensure compatibility with the latest WordPress releases.
   • Contact the plugin or theme developer’s support team to inquire about Gutenberg compatibility or seek assistance with any issues.
3. Inadvertent Re-Enabling Disable Gutenberg: WordPress occasionally updates its core components, and these updates can re-enable Gutenberg. To prevent this:
   • Regularly check your website after WordPress updates to ensure that the Classic Editor remains active. If necessary, revisit the ‘Disable Gutenberg’ plugin or Classic Editor settings and confirm your preferences.
   • If a WordPress update unexpectedly re-enables Gutenberg, simply follow the installation and activation steps for the Disable Gutenberg plugin again to regain control.
4. Compatibility with Custom Post Types: If you use custom post types on your website and encounter issues with Gutenberg, ensure that you’ve properly configured the ‘Disable Gutenberg’ plugin or Classic Editor settings for these post types.
   • Access the Disable Gutenberg plugin settings or the Classic Editor settings and verify that you’ve specified the default editor for the relevant custom post types.

By troubleshooting these common issues, you can ensure a smooth transition back to the Classic Editor while keeping Gutenberg disabled. Remember that even though you disabled Gutenberg, it’s still technically part of your WordPress. Eventually, your WordPress editor will “only” be the block editor.

Disable Gutenberg In Summary

In this article, I’ve taken you through the process of disabling Gutenberg, the Block Editor and keeping the Classic Editor as your default editing tool.

We began with the pros and cons of both editors, ensuring you had enough understanding of your options. From personal preferences to compatibility issues, we discussed the various factors that might lead you to choose the Classic Editor over Gutenberg.

As you move forward with WordPress, remember that your choice between Gutenberg and the Classic Editor should align with your needs and preferences. Disabling Gutenberg doesn’t mean resisting progress; it means choosing the editor that gives you peace of mind to create content efficiently and comfortably.