Classic Block Hidden from Inserter by Default in WordPress 7.1
Hide Classic block from inserter by default in WP 7.1; use wp_classic_block_supports_inserter filter to opt back in.
Add wp_classic_block_supports_inserter filter if you need Classic block in inserter.
Summary
WordPress 7.1 introduces a change that hides the Classic block (core/freeform) from the block inserter by default, while keeping the block registered and all existing Classic content fully functional. The change is purely about steering new content away from the legacy Classic block; existing blocks, the Classic editor, and TinyMCE remain untouched. To opt back in, developers can add a one‑line filter wp_classic_block_supports_inserter or use the small Enable Classic Block plugin. The change does not modify or migrate any content, and the Classic block continues to support the Convert to Blocks action. The core team also experiments with a deprecation notice that surfaces inside existing Classic blocks, offering one‑click actions to convert content to blocks or a Custom HTML block. The change is backward compatible, with no breaking changes to existing functionality.
This update is part of a longer‑term effort to make the Classic block fully opt‑in and eventually load TinyMCE only when needed, but the current release focuses solely on removing the block from the inserter.
The article explains the rationale, backward compatibility, and how to opt back in if required.
Key changes
- Classic block no longer appears in the inserter.
- Classic block remains registered and functional.
- Existing Classic blocks continue to render and be editable.
- Classic editor and TinyMCE remain unaffected.
- Opt back in via wp_classic_block_supports_inserter filter.
- One‑line filter or small plugin available to enable.
- No content migration or breaking changes.
- Deprecation notice experiment for migration actions.