Getting ready for WordPress 7.0 — three things to check now: PHP requirements, FSE migration, and editor extensions

rather than replacing it. Think of it as the 7.0-specific supplement.

Item 1 — PHP minimum requirement increase (W3 pattern 3 again)

covers a related symptom — even when PHP compatibility doesn’t cause a hard break, it can silently corrupt output in ways that are hard to trace. Worth having on the checklist alongside the version check.

Item 2 — FSE standardization and theme migration (W3 pattern 4 revisited)

was the 5.0 Gutenberg launch where editor extensions built for the Classic Editor stopped working. Gutenberg’s roadmap follows a phase structure — Phase 3 (collaborative editing, enhanced revision management, data library) continues that trajectory.

Collaborative editing changes the fundamental state management model of the editor. Third-party plugins that hook into editor internals — custom meta boxes, custom field UIs, sidebar extensions — face the same structural risk they faced in 5.0. The specific APIs differ, but the pattern is the same: a significant internal change in how the editor works causes adjacent extensions to lose their footing.

What you can check now:

• List your active editor extension plugins
  

  wp plugin list --status=active --format=table

  # Manually identify editor-adjacent plugins: ACF, Pods, Meta Box, custom meta boxes, etc.

• Check whether major vendors (ACF, Pods, Meta Box, WooCommerce block extensions) have announced Phase 3 compatibility


• For plugins where no Phase 3 announcement exists yet, identify potential alternatives and flag them for follow-up

Note: "we don’t use collaborative editing" doesn’t mean you’re unaffected. Internal API changes in Phase 3 can affect plugins even on sites where the collaborative features themselves are never used. The dependency is on the editor internals, not the end-user feature.

Summary — what to do before 7.0 drops

The common thread: starting this work after 7.0 is announced puts you under time pressure. Replacing plugins that don’t support PHP 8.x requires research, testing, and a migration window. Theme migration is a substantial project. Editor extension alternatives may need to wait for vendors to ship updates.

— applying to lower-risk sites first before production — is especially useful when you have a mix of sites at different levels of readiness.

The W series in full

Pattern knowledge from W3 is most useful before the upgrade, not after. Knowing that PHP requirement increases follow a predictable pattern is only actionable if you run the plugin audit before 7.0 drops, not after the first site breaks. The preparation window is now.