Per post type
Switch the classic editor on for posts, pages or any custom type — everything else keeps the block editor.
Classic Editor module
Bring back the classic editor — one post type at a time.
Keep the block editor where it helps and the familiar TinyMCE editor where it doesn’t. Choose exactly which post types open in the classic editor, right from your WPStack panel — no extra plugin, nothing added to your front end.
PostsClassic editor
PagesBlock editor
PortfolioClassic editor
Landing PageBlock editor
Posts → Classic
Per-type control
Included in every planNo add-on or upsell
Zero front-end weightAdmin-only — nothing ships to visitors
Set it in secondsTick a post type, save, done
Why it’s different
The classic editor, without the compromises
Not all-or-nothing, not a core hack, and not a byte on your front end — just a clean per-type switch.
One clear toggle
A single list with a Select-All switch and a live Classic / Block badge on every row.
The official switch
It uses WordPress’s own editor filters — no hacks, no patched core, no surprises.
Builder-friendly
Elementor, Divi, Beaver Builder and WPBakery load their own canvas, so they’re unaffected.
Familiar writing
The classic TinyMCE toolbar, classic meta boxes and shortcodes that behave the way they always have.
Nothing on the front end
Purely an admin setting — it never adds scripts or styles to your visitors’ pages.
How it works
Three ticks and you’re done
No configuration files, no code — just a checkbox per post type.
01
Activate the module
Flip Classic Editor on in WPStack → Modules. A Classic Editor screen appears in the menu.
02
Pick your post types
Open the settings and tick the types that should use the classic editor — or Select All.
03
Write as before
Those types now open in the classic editor; the rest keep the block editor. Switch back any time.
In your dashboard
One clean list of post types
Tick the types that should open in the Classic Editor — everything else stays on the block editor. A live Classic / Block badge shows each choice, with a Select-all toggle.
Plays well with others
Safe next to your builders and the block editor
Because it uses WordPress’s own editor switch, it composes cleanly with everything else. Page builders load their own canvas, and every post type you don’t pick keeps the block editor exactly as it was.
- Uses core’s own use_block_editor filters
- Only affects the post types you select
- Never forces the block editor back on elsewhere
- Governs post-type editors, not the Widgets or Site Editor
PostsClassic editor
PagesBlock editor
Landing pagesEdit with Elementor
Each post type opens in exactly the editor you chose — builders unaffected.
WordPress6.0+ (6.5+ recommended)
PHP7.4+ (8.1+ recommended)
ThemesWorks with any theme
Front endNo scripts or styles added
Heads up: run only one classic-editor controller — if the official Classic Editor or Disable Gutenberg plugin is active, the settings screen will let you know.
FAQ
Classic Editor, answered
No — it’s per post type. Only the types you tick use the classic editor; everything else keeps the block editor, so you get the best of both.
Not at all. It’s an admin-only setting that changes which editor loads. Nothing is added to your front-end pages.
Yes. Page builders open their own editing canvas regardless of the WordPress editor, so this choice doesn’t affect them.
You can, but you shouldn’t — both control the same WordPress switch. Keep only one; the settings screen warns you if it detects the other.
Yes. Switching a type to the classic editor shows existing content as its underlying markup — nothing is deleted, and you can switch back any time.
Yes — like every WPStack module, Classic Editor is included in every plan. Switch it on per project from the modules panel.
Stop juggling plugins. Start with WPStack.
One system for forms, fields, the classic editor, bookings, logins and everything in between. Activate what you need today.
No credit card to explore the demo · Cancel anytime