Overview
WordPress 7.0 is scheduled for release on April 9, 2026. This issue tracks the work needed to ensure CoBlocks is fully compatible. Beta 1 is already available for testing.
Critical: Post Editor Always Iframed (Block API v2 Deprecated)
This is the highest-risk change for CoBlocks.
In WordPress 7.0, the post editor will always run inside an iframe, removing the legacy fallback that previously allowed blocks using API v1/v2 to opt out. Block API v2 has been deprecated since WP 6.9.
Affected CoBlocks blocks
Explicitly on apiVersion: 2 (must be migrated to v3):
click-to-tweet
counter
gallery-masonry
gallery-stacked
highlight
testimonials/testimonial
No apiVersion declared (default to v1 — also deprecated): 51 additional block.json files across the plugin need auditing.
Migration requirements
- Update
apiVersion to 3 in all block.json files
- Audit JS in each block for use of global
document or window — these will break in the iframe context where the editor's document is different from the admin page
- Replace any direct DOM access with
useRefEffect or other iframe-safe APIs
- Reference: Migrating Blocks for iframe Editor Compatibility
Additional Changes to Assess
HtmlRenderer component (Gutenberg 22.4): Several blocks will lose an extra wrapping <div> in the editor — verify styling is consistent between editor and front end
- New global block supports (text indent, text columns, image aspect ratios for wide/full): Check if CoBlocks' custom implementations conflict with new core features
isNotAll operator deprecated in query APIs — may affect the Posts block
theme.json link underline removed — audit any styling that relied on this default
- PHP minimum raised to 7.4 — CoBlocks already requires 7.4, so no change needed here
CI Updates Required
The test-wp-next.yml workflow needs to be updated:
scheduled_release_date is stale (set to 2024-04-02)
wp_next URL still points to wordpress-6.8-RC2.zip
- Update to point at WordPress 7.0 beta/RC zip and adjust
installPath
Checklist
Overview
WordPress 7.0 is scheduled for release on April 9, 2026. This issue tracks the work needed to ensure CoBlocks is fully compatible. Beta 1 is already available for testing.
Critical: Post Editor Always Iframed (Block API v2 Deprecated)
This is the highest-risk change for CoBlocks.
In WordPress 7.0, the post editor will always run inside an iframe, removing the legacy fallback that previously allowed blocks using API v1/v2 to opt out. Block API v2 has been deprecated since WP 6.9.
Affected CoBlocks blocks
Explicitly on
apiVersion: 2(must be migrated to v3):click-to-tweetcountergallery-masonrygallery-stackedhighlighttestimonials/testimonialNo
apiVersiondeclared (default to v1 — also deprecated): 51 additionalblock.jsonfiles across the plugin need auditing.Migration requirements
apiVersionto3in allblock.jsonfilesdocumentorwindow— these will break in the iframe context where the editor'sdocumentis different from the admin pageuseRefEffector other iframe-safe APIsAdditional Changes to Assess
HtmlRenderercomponent (Gutenberg 22.4): Several blocks will lose an extra wrapping<div>in the editor — verify styling is consistent between editor and front endisNotAlloperator deprecated in query APIs — may affect the Posts blocktheme.jsonlink underline removed — audit any styling that relied on this defaultCI Updates Required
The
test-wp-next.ymlworkflow needs to be updated:scheduled_release_dateis stale (set to2024-04-02)wp_nextURL still points towordpress-6.8-RC2.zipinstallPathChecklist
test-wp-next.ymlto target WP 7.0 Beta 1block.jsonfiles — identify which needapiVersion: 3apiVersion: 3document/windowglobal access in iframe-unsafe waysreadme.txtandpackage.jsontested_up_toto7.0