Disable Gutenberg replaces WordPress's block editor with the classic editor. Use this if you prefer the traditional writing experience or if your workflow is incompatible with blocks.
What this feature does
WordPress introduced the Gutenberg block editor as the default post and page editor. Gutenberg organizes content into blocks (paragraphs, images, buttons, etc.) and uses a visual builder interface. While powerful, some users prefer the simpler classic editor with a single text area.
This setting disables Gutenberg entirely and restores the classic TinyMCE editor for all post types. It also disables the block editor in the widgets panel and removes Gutenberg's stylesheets and assets from the front-end, reducing page weight slightly.
If your team is used to the classic editor, or if you have custom post types or plugins that aren't fully compatible with blocks, disabling Gutenberg removes the complexity. You can still use all WordPress features; just with a simpler, more familiar interface.
How to enable it
- Open AdminEase and navigate to Posts. Click AdminEase in the WordPress admin menu, then switch to the Posts tab.
- Toggle Disable Gutenberg on. Save the setting. Changes take effect immediately on the next page refresh.
- Verify in the post editor. Create a new post or edit an existing one. You should see the classic TinyMCE editor instead of the block editor interface. All your familiar formatting buttons are there.
- Check the widgets area. Go to Appearance > Widgets. The widgets editor should also use the classic interface instead of blocks.
Settings reference
| Setting | What it does | Default |
|---|---|---|
| Disable Gutenberg | Disables the Gutenberg block editor globally and restores the classic TinyMCE editor for all post types and pages. Also disables the block editor in the widgets panel. Removes Gutenberg assets from the front-end to reduce page weight slightly. | Off |
| Post types Pro | Select specific post types to disable Gutenberg for. If left empty, Gutenberg is disabled for all post types. Pro only. | (empty) |
What happens behind the scenes
AdminEase disables Gutenberg by removing it from several hooks and filters:
use_block_editor_for_post_type: Prevents the block editor from loading for any post typegutenberg_can_edit_post_type: Blocks Gutenberg at the Gutenberg plugin level (for compatibility)use_block_editor_for_post: Additional fallback to disable blocks on individual postsgutenberg_use_widgets_block_editoranduse_widgets_block_editor: Disable the block editor in widgetswp_enqueue_scripts: Removes Gutenberg stylesheets and assets from the front-end
The classic TinyMCE editor is WordPress's built-in fallback and loads automatically when Gutenberg is disabled.
Troubleshooting
I disabled Gutenberg, but I still see the block editor
Clear your browser cache completely, including cached JavaScript. The admin interface sometimes caches editor scripts. Also make sure you're using a modern browser that supports the classic editor. If the block editor persists after a full cache clear and browser refresh, confirm the setting was saved correctly in AdminEase > Posts.
Can I re-enable Gutenberg for specific post types?
With the free version, Gutenberg is disabled globally for all post types. However, AdminEase Pro includes a child field that lets you select specific post types to disable Gutenberg on, while keeping it enabled for others. This is useful when you want the classic editor for posts but need Gutenberg for custom post types or pages.
Will my existing block-based posts still work?
Yes. If you had posts created in the block editor and then disabled Gutenberg, those posts still display correctly on the front-end. You just can't edit them in the block editor anymore. When you open them for editing, they'll appear as raw block code in the classic editor, which can look messy but won't break your site. To edit them cleanly, re-enable Gutenberg temporarily, edit the post, then disable it again.
Does this affect the WordPress admin bar or dashboard?
No. The admin bar, dashboard widgets, and other admin interfaces are unaffected. Only the post and page editors, and the widgets editor, revert to classic. Everything else works as normal.