7 posts tagged with "migration"

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.

Drupal core is drawing a clean boundary for Drupal 12: the general Migrate API stays, but the Drupal 6/7 source migration path shipped as migrate_drupal and the old browser workflow shipped as migrate_drupal_ui are being removed from core.

That is not just housekeeping. It changes how Drupal 10 and Drupal 11 teams should structure their modernization programs right now, especially agencies and platform teams still treating "upgrade to the next major" and "migrate from an old site" as one blended workflow.

The Drupal Module Upgrader (DMU) is active again, and that matters for teams still porting Drupal 7 custom modules into modern Drupal codebases.

The key update is concrete: on March 5, 2026, drupalmoduleupgrader published 2.0.0-alpha2 with Drupal 10/11 compatibility. But the project page still states it is on "life support," minimally maintained, and feature-complete from the maintainers' perspective. That combination tells you exactly how to use it: as a migration accelerator, not as an autopilot.

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.

WordPress 6.9 added assertEqualHTML(), which removes a whole category of brittle test failures caused by formatting-only HTML differences. I reviewed the implementation and mapped out concrete migration patterns for plugin and theme test suites.

If your test suite has ever failed because of a whitespace difference in rendered HTML, this is for you.

Cloudflare viNext is the fastest path today to run modern Next.js apps on Workers with less adapter glue. But the safe adoption pattern is not "AI rewrites everything." The practical pattern is AI for scoped transforms, deterministic checks for every change set, and a canary rollback plan.

That combination gives speed without losing production stability.

I shipped a Drupal migrate mapping validator utility that catches broken mappings before they land in prod.