July 10, 2026 update: WordPress Core has reversed the earlier WordPress 7.1 Classic block inserter plan. The Classic block remains available in the inserter by default for WordPress 7.1, so this checklist now focuses on cleanup and verification instead of an urgent workaround.
If you own or maintain a WordPress site with older content, the practical answer is simple: do not rush a Classic block migration because of the June proposal alone. Existing Classic blocks remain editable, and new Classic blocks can still be added through the normal editor paths.
What Changed Since The June Proposal
The June 23 proposal said WordPress 7.1 would hide the Classic block from the inserter while keeping existing Classic blocks editable. On July 7, WordPress Core posted the follow-up: the Classic block remains available in the inserter, block library, and slash-command flow.
- Classic block remains available in WordPress 7.1 by default.
- The
wp_classic_block_supports_inserterfilter has been removed because the planned behavior is no longer shipping in that form. - The block-level migration notice has been removed.
- The Enable Classic Block plugin will be closed. If you installed it only for this change, you can remove it after confirming editing still works normally.
What Site Owners Should Do Now
There is no emergency migration requirement from this specific WordPress 7.1 change. Still, older Classic block content is worth inventorying because it often points to old editor workflows, shortcodes, builder leftovers, or staff documentation that has not been reviewed in years.
- Take a current backup before changing editor plugins or bulk-editing older posts.
- Check a staging copy of the site with the current WordPress 7.1 testing build or Gutenberg test setup if you already maintain one.
- Open representative posts that use Classic blocks and confirm they edit, save, preview, and publish cleanly.
- If you added Enable Classic Block only because of the June plan, deactivate it on staging first, then remove it on production after a clean editor check.
- Keep any planned Classic-to-block cleanup as a normal content maintenance project, not as a rushed release-day task.
Agency And Client Notes
Agencies should update any client memo that said the Classic block was disappearing from the inserter in WordPress 7.1. That was valid planning language for the June proposal, but it is no longer the current WordPress Core direction.
The better client message is: WordPress 7.1 keeps the Classic block visible, but old Classic content should still be reviewed during normal maintenance. That keeps the work accurate without creating false urgency.
Safe Verification Checklist
For production sites, keep the verification boring and repeatable:
- Confirm the site has a usable backup.
- Search the post list for content that still uses Classic blocks.
- Open one older Classic-heavy post in staging and confirm the editor behaves normally.
- Confirm the Classic block appears when you search the inserter.
- Save a draft or staging-only test update and verify the public preview.
- Remove temporary opt-in tooling only after the staging check passes.
Sources Checked
This update is based on the official Make WordPress Core follow-up from July 7, 2026, the original June 23 proposal, the public Gutenberg tracking issue, and the WordPress.org Enable Classic Block plugin page. The Repository also surfaced the reversal in its WordPress news coverage, but the site guidance above is anchored to the official Core source.
