6 posts tagged with "compatibility"

On March 15, 2026, WordPress core published a set of WordPress 7.0 dev notes covering five block-editor changes that matter more than they first appear: pattern editing defaults, viewport-based block visibility, per-block custom CSS, expanded dimensions support, and native text-indent controls.

None of these are headline platform shifts like the Interactivity API or collaboration work. They are more practical than that. They change what editors can do without custom code, what block authors should opt into or opt out of, and where plugin and theme teams can finally stop carrying custom UI or CSS debt.

As of February 27, 2026, WordPress 7.0 Beta 2 (released February 26, 2026) is in active testing ahead of the planned final release on April 9, 2026. I reviewed what can break for custom plugins and themes, and built a minimal checklist to reduce upgrade risk.

As of February 25, 2026, the short answer is: move production to Node 24.14.0 LTS first, test Node 25.7.0 in a non-blocking lane, and treat native addons plus framework engine ranges as the main risk surface. Both were released on February 24, 2026, but 25.x is still the Current line while 24.x is LTS.

As of February 24, 2026, WordPress 7.0 is in Beta 1 (released February 20, 2026), and the post editor is planned to run inside an iframe regardless of block apiVersion. If your plugin still depends on top-window DOM selectors, legacy block registration, or unflagged classic meta boxes, this is the migration window to fix compatibility before the planned 7.0 release on April 9, 2026.

I built a WordPress 7.0 compatibility scanner CLI that detects deprecated editor integrations and iframe-unsafe code patterns in plugins/themes. It gives rule IDs, migration replacements, and CI exit codes so teams can block risky code before release windows.

I distilled WordPress 6.9.1 RC1 into a compatibility checklist for plugins and themes before the maintenance release landed. I also packaged the checklist and notes into a small repo so teams can clone it and wire it into their own QA flow.