WordPress 7.0 was released on 20 May 2026 — the first major version
of the year. Below is a summary of what changed, what was pulled before
release, and how we’re handling the update across the sites we
maintain.
What was pulled before
release
Real-time collaborative editing — the “two people editing the same
post at once” feature that dominated pre-release coverage — is not in
WordPress 7.0. The core team pulled it on 8 May 2026, citing race
conditions, server load and memory efficiency issues uncovered during
stability testing. It is expected to ship in WordPress 7.1 or later.
What shipped
Native AI infrastructure
WordPress 7.0 introduces three connected pieces of AI plumbing:
- The Connectors screen (Settings → Connectors). A
single place to enter API keys for OpenAI, Anthropic and Google.
Previously each AI plugin stored its own keys. - The WP AI Client. A provider-agnostic API plugins
can call. Switching providers at the Connectors level does not require
reconfiguring each plugin. - The Abilities API and MCP Adapter. Lets WordPress
expose site actions (create a post, update an order, generate alt text)
in a structured way that external AI agents can discover via the Model
Context Protocol.
Out of the box, none of this changes how a site behaves. AI features
only appear once a provider is connected and a compatible plugin is
installed.
Admin dashboard rebuild
(DataViews)
The Posts, Pages and Media list screens have been replaced by
DataViews — a React-based interface with filtering, layout switching and
bulk actions built in. It is the first overhaul of these admin screens
since 2013.
Sites with heavily customised admin screens — some WooCommerce
stores, membership sites, custom workflow plugins — are the highest-risk
category for compatibility issues.
PHP requirement raised
WordPress 7.0 requires PHP 7.4 as the minimum, with PHP 8.3
recommended. Sites still on PHP 7.2 or 7.3 will not be offered the
update — the dashboard holds them on the 6.9 security branch.
PHP version can be checked under Tools → Site Health → Server. PHP
8.2 itself reaches end-of-life in December 2026, so any site running
anything below 8.3 should be on a roadmap to upgrade.
Smaller additions
- Two new core blocks: Breadcrumbs (with schema
markup built in) and Icons - The Font Library now works on classic themes,
previously block themes only - Per-block custom CSS and responsive
visibility controls (show or hide a block by device without a
plugin) - Cover blocks accept video URLs instead of requiring an upload
- Client-side media processing for image resizing
- A keyboard-driven command palette (Cmd+K / Ctrl+K) for admin
navigation
Several of these replace functionality currently handled by
third-party plugins, which has knock-on effects for the plugin footprint
of a typical site.
Specific risks for business
sites
- WooCommerce stores with custom checkout flows.
DataViews touches order list screens. Most major extensions have been
updated; heavily customised setups carry the most compatibility
risk. - Sites with older premium plugins. Check whether the
vendor is still actively maintaining the plugin before updating. - Custom admin extensions and meta boxes. The
React-based admin rewrite can affect bespoke admin UIs. - Sites still on PHP 7.x. Even where the update is
technically possible, PHP 8.3 should be on the roadmap before end of
2026.
Practical notes on the AI
features
For sites considering switching on the new AI infrastructure, three
points are worth flagging:
- API costs are billed to the provider account, not via
WordPress. A misbehaving or looping plugin can run up a bill
quickly. Set hard spending caps in the provider account before enabling
anything. - The Abilities API grants plugins permission to trigger
actions. Audit which plugins have which abilities before
granting anything that can publish content, modify users or change
settings. - WordPress 7.0 does not include AI features itself.
It provides the plumbing. A separate plugin is still needed to actually
use AI on the site.
What WP Care clients don’t
need to do
Sites on a managed plan don’t require any action. We’re working
through the portfolio in the order above — staging first, low-risk
production next, complex sites once the plugin ecosystem catches up. If
a site needs input — a deprecated plugin, a theme that needs replacing,
a PHP version that needs lifting — we will come back with the options
and a recommendation.
For self-managed sites
- Take a full off-server backup
- Confirm PHP version is 8.2 or higher (Tools → Site Health →
Server) - Test on staging before updating production
- Wait for the 7.0.1 point release before updating any
business-critical site
For a once-over on whether a site is ready for 7.0, or to have
the update handled across the board, get in touch or see our managed WordPress care
plans.
