WordPress 7.0 Is Coming: Why Your PHP Version Matters More Than Ever

Why the WordPress 7.0 release was delayed and what it means for your site

In late March 2026, the WordPress release team announced an extended timeline for version 7.0. The reason is a structural problem with the Real-Time Collaboration (RTC) feature. The current implementation stores sync data using post_meta on a special internal post type, which disables WordPress persistent post query caches whenever a user has the editor open. The proper fix requires a dedicated database table, not a last-minute patch. A revised schedule will be published no later than April 22nd, 2026. The practical takeaway for site owners: do not rush the update on production sites the moment the final release appears. Wait a few days, read the release notes, and verify plugin compatibility before upgrading.

The PHP minimum is changing: check your hosting environment now

• PHP 7.2 and 7.3 are no longer supported as of WordPress 7.0. Running either version when you update can cause errors or unpredictable behavior.
• PHP 7.4 becomes the new minimum requirement. Your server must run at least this version to install or update to WordPress 7.0.
• PHP 8.2 or 8.3 is recommended for the best performance and compatibility with new core features.
• In the Mioritic Host control panel (cPanel or Plesk), you can change the PHP version per domain using MultiPHP Manager or PHP Settings, without affecting other sites on the same account.
• Before switching PHP versions, take a full site backup and test on a staging environment if you rely on older plugins or custom themes.

What else is new in WordPress 7.0 for developers and site admins

Beyond RTC, WordPress 7.0 ships several changes worth knowing about if you build or manage WordPress sites:

WP AI Client is a new core PHP library that provides a standardized interface for AI services such as OpenAI, Anthropic, and Google. Instead of each plugin integrating directly with a provider, the abstraction layer means switching providers becomes a configuration change rather than a code rewrite. Connectors API lets site owners configure AI providers directly from the WordPress admin, using official plugins available in the WordPress.org directory. Client-Side Abilities API brings the permissions system introduced on the PHP side in WordPress 6.9 to JavaScript, laying the groundwork for browser agents and WebMCP integration. On the editor side, users get live previews of block style variations, a new Playlist block with waveform audio visualization, and the ability to add navigation links directly from the List View sidebar without opening the editor canvas.

Rolling back to beta status after entering the Release Candidate phase is unprecedented, but the reasoning is sound: an architectural performance issue should not be patched at the last minute before shipping to millions of sites.

If your plugins or themes still use add_meta_box(), now is a good time to migrate to register_post_meta() and the PluginSidebar component — classic meta boxes will disable collaboration mode for a post in WordPress 7.0. If you manage multiple client sites, audit the PHP version on each account in your hosting control panel before automatic updates run. At Mioritic Host, PHP version is configurable per domain, giving you precise control without unnecessary risk. The safest workflow: update a staging or test site first, confirm everything works as expected, then roll out to production.