Choosing and managing the classic editor
Classic Editor restores the previous editing screen and lets administrators decide how people use it. Administrators can set the default editor for everyone and allow users to switch; when switching is enabled, users can choose an editor for each post. Posts reopen in the editor last used for them, even if a different person edited the post most recently.
Settings are managed under Settings → Writing. This gives site owners a central way to set editing behavior, while per-post choices help teams with mixed preferences.
Legacy editor extensions and block-theme limits
The plugin is designed for older editing workflows, but it does not support full site editing or block themes.
- Legacy extensions: Supports plugins that extend the previous Edit Post screen, including those that add old-style meta boxes. This can help preserve tools built for that interface.
- Developer controls: Filters let other plugins manage settings and editor choices by post or post type, giving sites a way to tailor editing rules.
- Theme limitation: Block themes rely on blocks and are not supported for this classic-editor workflow, so check the theme setup before adopting it.
Broad adoption with a support record to monitor
Classic Editor has broad adoption and an excellent rating, while its visible support activity is limited.
The plugin is described as among the directory’s most widely installed and is maintained by the WordPress team. Its latest version is 1.7.0, updated in late May. These signals point to a mature, established option, though the update is not especially recent.
Three support threads are visible, and none are marked resolved. That is a small support sample rather than proof of poor maintenance, but site owners who depend on prompt help should account for the limited visible resolution record. It suits teams committed to the classic editing screen, especially where legacy extensions matter; block-theme sites should look elsewhere for an editing workflow.
