Disable Gutenberg and Get the Classic Editor Back

Bring back the classic WordPress editor globally, per post type, per role or post, plus classic widgets and block-CSS cleanup, in one Essentials module.

I still write most of my posts in the classic editor. Not out of stubbornness—for straight text, the block editor’s panels, popovers and ”+” buttons are friction I don’t need. But the usual advice, “install the Classic Editor plugin,” is blunt: it flips Gutenberg off site-wide, with at most a per-user opt-out—no rule per post type, none per role. What I actually want is nuance—classic for blog posts, blocks for landing pages, the simple editor for the client, the full one for me. Here’s how to disable Gutenberg with that kind of control, and clean up what it leaves running while you’re at it.

The essentials

  • The module makes the classic editor the default, but the real value is granularity: choose the editor per post type, per role, or per individual post (once you let users switch editors).
  • It restores the classic Widgets screen (WordPress switched widgets to blocks too), on by default.
  • It removes the block library’s front-end CSS by default on the pages of a classic theme that use no blocks—WordPress otherwise loads it on every page—and can strip it in the admin too.
  • It stops Gutenberg fetching remote block patterns from the WordPress.org API, so the editor doesn’t call WordPress.org for them.
  • Once you let users switch editors, the posts list gets Edit (Block) / Edit (Classic) links, the choice is remembered per post, and each user can pick a personal default editor in their profile.

Why do people still disable the block editor?

People still disable the block editor because a lot of WordPress work isn’t layout, it’s writing: for a text-first blog, a business site, or a client who just needs to update a page, the classic TinyMCE editor is faster and less intimidating than blocks, side panels and a ”+” button on every line. Gutenberg is good at building complex layouts; the common reasons to switch it off are elsewhere:

  • You write mostly text and don’t need block-based layouts.
  • You use a page builder (Elementor, Divi, Beaver Builder) that brings its own editing canvas anyway.
  • You manage a site for a client who finds blocks confusing.
  • You want a lighter, quicker admin.

None of these mean “kill Gutenberg forever, everywhere.” Which is exactly the problem with the usual on/off approach.

How do you disable Gutenberg—everywhere or just where you want?

Activate the Classic Editor module in Blaminhor Essentials: out of the box it sets the classic editor as the site default, so posts and pages open in familiar TinyMCE with no blocks, no side panels, no ”+” button. Then override it where you want blocks back—per post type, per user role, or on a single post—from the same settings page.

Illustration: two document cards side by side—one filled with coloured blocks, the other with plain lines of text. Blocks on the left, plain text on the right. In the module itself, you set the default editor, then override it by post type, by role, or on a single post.

The editor is resolved from the most specific rule to the most general—the first match wins:

LevelWhat it setsExample
Single postPer-post editor choice (with switching enabled)Force blocks on one landing page
Post typeClassic or blocks for a whole typePosts classic, pages on blocks
User roleEditor decided by who’s logged inClassic for clients, blocks for you
User preferenceA personal default each user picks in their profile (with switching enabled)You prefer blocks, a colleague prefers classic
Global defaultThe fallback for anything not overriddenClassic everywhere by default

Mind the order: a post-type rule beats a role rule. If posts are set to classic, an administrator whose role says “blocks” still gets the classic editor on posts—use a per-post override for the exceptions.

That layering is the difference between “I turned Gutenberg off” and “I put the right editor in front of each person and each content type.”

What does disabling Gutenberg clean up behind the scenes?

Disabling Gutenberg with the module also restores the classic Widgets screen, stops loading the block library’s stylesheet on classic-theme pages that render no blocks, and stops the editor fetching block patterns from WordPress.org—three things you don’t see, all on by default where they’re safe. One optional extra strips the block styles from the admin too.

Classic Widgets come back. WordPress didn’t only move the editor to blocks—it did the same to the Widgets screen. The module restores the traditional Widgets interface so your sidebar and footer widgets behave the way they always did.

Block CSS stops loading. WordPress enqueues the block library’s stylesheet on every front-end page, even one that contains no blocks at all. On a classic theme, the module removes it by default from every page that renders no blocks, trimming kilobytes and an HTTP request off each page load (a block theme keeps it, since its templates are blocks), and can strip the block styles from the admin too if you want an even leaner backend. It also stops Gutenberg fetching remote block patterns from the WordPress.org API, so the editor doesn’t call WordPress.org for them.

Why use the module rather than the official Classic Editor plugin?

The official Classic Editor plugin works and is maintained, but its settings stop at a site-wide default plus an optional per-user choice: no rule per post type, none per role. The Classic Editor module in Blaminhor Essentials adds those two levels, keeps the per-user and per-post switching, and saves you one more plugin to install, update and watch for conflicts. If you’re already running Blaminhor Essentials, the module is a toggle away.

If the per-role angle interests you—handing different users different experiences—it pairs neatly with managing WordPress user roles, where you shape what each role can see and do.

Classic Editor is one of the 26 modules in Blaminhor Essentials—free and open-source on WordPress.org.

Download Blaminhor Essentials

– blaminhor

FAQ

Can I keep Gutenberg for pages but use the classic editor for posts?

Yes. The Classic Editor module resolves the editor per post type, so you can set posts to classic and leave pages on the block editor (or the reverse). It can also decide by user role, and it remembers a per-post choice when you enable switching—far more granular than an all-or-nothing toggle.

Is the Classic Editor going away?

The official Classic Editor plugin's own page says it will be fully supported and maintained 'until 2024, or as long as is necessary', so it isn't disappearing any time soon. A module that restores the classic editor achieves the same result without depending on one plugin's lifecycle, and adds per-type and per-role control the official plugin doesn't offer.

What's the difference between Gutenberg and the Classic Editor?

Gutenberg is the block editor: you build content from stackable blocks — paragraphs, images, columns — with side panels and a floating toolbar. The Classic Editor is the older TinyMCE box, a single formatted text area much like a word processor. Blocks suit rich layouts; the classic editor suits fast, text-first writing with far less on-screen furniture.

How do I disable Gutenberg without a plugin (functions.php)?

You can add a filter to functions.php: return false from the 'use_block_editor_for_post' hook to force the classic editor everywhere. It works, but it's blunt and lives in your theme, so it vanishes on a theme switch and gives no per-type or per-role control. A dedicated module is more durable and far more flexible.

Will switching to the Classic Editor break my existing block posts?

Not the underlying content, but it looks messy. Switching a block-built post to TinyMCE shows the raw block markup — those '<!-- wp:paragraph -->' comments — instead of a clean layout. Keep existing block posts on the block editor with a per-post override (after enabling 'Let users switch editors'), or clean the markup once before you switch them over.

Do I need the Classic Editor if I use a page builder like Elementor?

Usually not for the builder itself — Elementor, Divi and Beaver Builder bring their own canvas and bypass Gutenberg on the pages they edit. But posts and other content still open in the block editor, so many people pair a builder with the classic editor to keep everything else simple and consistent.

blaminhor Building what's missing.

Comments