Repository navigation
Classic block: Remove migration notice and restore inserter availability - #79894
Merged
Merged
Conversation
Remove the Freeform (Classic) block migration notice and revert the Classic block deprecation UX to its pre-experiment state, restoring the "Convert to blocks" toolbar button and the original placeholder. Also stop hiding the Classic block from the inserter: drop the `window.__needsClassicBlock` gate in `freeform/init` and remove the `wp_classic_block_supports_inserter` filter, which never shipped in a WordPress release, along with its tests. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
tyxla
added
Needs PHP backport
commented
Jul 6, 2026
|
Size Change: -290 B (0%) Total Size: 7.67 MB 📦 View Changed
|
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
10 of 37 tasks
tyxla
marked this pull request as ready for review
July 6, 2026 12:21
tyxla
requested review from
ajitbohra,
fabiankaegy and
spacedmonkey
as code owners
July 6, 2026 12:21
tyxla
added
[Block] Classic
commented
Jul 6, 2026
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
commented
Jul 6, 2026
Member
Author
|
Going to merge - the e2e test failure is not related, and is also failing on this PR: #79886 |
t-hamano
added
the
Backport to Gutenberg Minor Release
commented
Jul 13, 2026
Contributor
|
This PR was manually cherry-picked to the |
t-hamano
removed
the
Backport to Gutenberg Minor Release
9 tasks done
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What?
This reverts the recent Classic (Freeform) block deprecation work:
window.__needsClassicBlockgate infreeform/init.wp_classic_block_supports_inserterfilter (and its PHP tests). This filter never made it into a WordPress release.Why?
The deprecation notice and inserter gating are being reverted. The inserter-gating filter never shipped in a WordPress release, so it can be removed cleanly.
See #78067 (comment) for more info.
How?
packages/block-library/src/freeform/migration-notice.jsand revertedfreeform/edit.jsto its pre-experiment state, re-addingfreeform/convert-to-blocks-button.js.freeform/inittoinitBlock( { name, metadata, settings } )sosupports.inserterfalls back to itstruedefault.lib/compat/wordpress-7.1/classic-block.phpand itsrequireinlib/load.php, and removed the corresponding tests inphpunit/script-loader-test.php.classic.spec.jsE2E assertions to click the "Convert to blocks" toolbar button.Testing Instructions
🤖 Generated with Claude Code