Classic Editor
v1.0.2Bring back the familiar TinyMCE editor — per post type. Choose which content types open in the Classic Editor; everything else keeps the block editor.
Overview
The Classic Editor module lets you decide, per post type, which content opens in the classic TinyMCE editor instead of the block editor.
Some sites — and some clients — are simply happier in the classic editor: familiar TinyMCE toolbar, classic meta boxes, and shortcodes that behave the way they always have. Rather than switching the whole site, this module lets you keep the block editor where it helps and the classic editor where it doesn’t, per post type.
- Turn the classic editor on per post type — posts, pages, or any custom type
- Everything you don’t pick keeps the block editor
- One Select All toggle, with a live Classic / Block badge per row
- Uses WordPress’s own editor switch — no hacks, no front-end weight
- Plays nicely with page builders and the rest of your stack
Requirements & compatibility
It runs on any WordPress site and works with any theme.
| Requirement | Minimum | Recommended |
|---|---|---|
| WordPress | 6.0 | 6.5 or newer |
| PHP | 7.4 | 8.1 or newer |
| Themes | Any theme | Any theme (block or classic) |
Installation & activation
Classic Editor ships inside WPStack — switch it on and pick your post types.
Activate the module
In WPStack → Modules, flip Classic Editor on. A Classic Editor item appears in the WPStack menu.
Open its settings
Go to WPStack → Classic Editor to see every editable post type as a checkbox.
Tick the post types
Enable the classic editor for the types you want (use Select All for everything), then Save.
Choosing editors per post type
The settings screen is one list — every UI-visible post type, with a badge showing which editor it uses.
- Each row is a post type with a Classic / Block badge that flips live as you toggle it.
- Select All (top and bottom) turns the classic editor on for every type at once.
- Ticked types open in the classic editor; unticked types stay on the block editor.
- Attachments and non-UI post types aren’t listed — they can’t use a post editor.
portfolio) to the classic editor for straightforward writing.How it fits with other plugins
It uses WordPress’s official editor-switch, so it composes cleanly with the rest of your stack.
- Page builders (Elementor, Divi, Beaver Builder, WPBakery) load their own canvas and are unaffected.
- It only sets the choice for post types you selected — it never forces the block editor back on elsewhere.
- It governs the post-type editors only, not the Widgets screen or the block-theme Site Editor.
Frequently asked questions
No — it’s per post type. Only the types you tick use the classic editor; everything else keeps the block editor.
No. It’s an admin-only setting that changes which editor loads — it adds nothing to your front-end pages.
Yes. Builders open their own editing canvas regardless of the WordPress editor, so the choice here doesn’t affect them.
You can, but you shouldn’t — both control the same WordPress editor switch. Keep only one; the settings screen warns you if it detects the other.
Switching a type to the classic editor shows existing block content as its underlying markup — nothing is deleted. Switch back to the block editor any time.