WordPress 7.0 Is Here. Here’s How We’re Handling It for Our Maintenance Customers.
WordPress 7.0 dropped today (May 20, 2026), and it’s one of the most architecturally significant core releases we’ve seen in years. New AI integration infrastructure baked into core, a completely overhauled admin experience, and a fresh developer API surface. It’s a lot, and a lot of it is brand new code touching parts of WordPress that haven’t changed much in years.
At Blue Arctic, we’ve already started staging and compatibility testing across managed maintenance customer environments before production rollout begins.
If you’re a Blue Arctic website maintenance customer, you don’t have to think about any of this. We’re already on it. Here’s what’s in the release, what we’re watching for, and how we’re approaching the rollout.
What’s actually in WordPress 7.0
A few things to know up front. Real-time collaborative editing was pulled from this release. It was the headline feature for months, but the core team ran into too many issues during testing and pushed it to 7.1. That’s actually a good sign that the project is prioritizing stability over hitting dates.
Here’s what did ship:
WP AI Client
WordPress now has a standardized, provider-agnostic API for connecting to external AI services. No model is bundled with core. Instead, plugins and themes can register providers (OpenAI, Anthropic, whatever) through one unified interface. There’s also a new Connectors UI under Settings where site owners can manage those external AI connections.
DataViews admin redesign
The old WP_List_Table screens (posts, pages, users, media) are being replaced with a React-based interface called DataViews. Faster filtering, better sorting, app-like feel. It’s a noticeable visual change for anyone who spends time in wp-admin.
Because DataViews replaces legacy admin interfaces WordPress has relied on for years, we’re paying especially close attention to plugins and custom tooling that hook into older admin screens.
Abilities API and Client Side Abilities API
New developer hooks that let plugins and themes register capabilities the AI client can call. This is the foundation for AI-aware plugins down the line.
PHP-only block registration
Developers can now register functional blocks without writing JavaScript. Inspector controls are auto-generated. Smaller plugin footprints, less maintenance burden.
Minimum PHP bumped to 7.4
PHP 8.3+ is recommended. This one isn’t a concern for any of our maintenance customers. Every site we maintain is already running PHP 8.3 or higher, and that’s not by accident. It’s policy.
Why we’re not pushing this to production sites yet
Here’s the part that separates managed WordPress maintenance from a Thursday morning click on the “Update Now” button.
A point-zero release of WordPress is never the version you want running on a site that pays your bills.
The 7.0 codebase is the result of merging Gutenberg plugin versions 22.0 through 22.6 into core, plus a complete admin UI rewrite, plus a new API layer. Even with a thorough RC cycle, edge cases show up in the wild that no amount of testing catches.
Theme compatibility quirks. Plugin authors who haven’t tested against the new DataViews screens. Sites running older PHP that suddenly throw fatals.
Usually the biggest issue after a major WordPress release isn’t WordPress core itself. It’s the plugin ecosystem catching up afterward.
So we’re not updating anyone’s production site today. That’s the whole point of having us in the loop.
A quick note on PHP, because it matters here
Every WordPress site we maintain runs on the latest stable PHP. Right now that’s 8.3 or higher.
We don’t make exceptions for “this old plugin needs 7.4” or “the theme breaks on 8.2.” If a theme or plugin holds a site back from running modern PHP, we rebuild it so it doesn’t.
There are two reasons we operate this way, and both matter for a release like WordPress 7.0.
Security
Old PHP versions stop getting security patches. Running a site on PHP 7.4 in 2026 means you’re exposed to vulnerabilities that have been public for years and will never be fixed in your version.
We’re not willing to take that risk for our customers, and we don’t want our infrastructure hosting that risk either.
Performance
PHP 8.3 is dramatically faster than 7.4 on real-world WordPress workloads. Pages render quicker, the admin feels snappier, and the server handles more concurrent traffic on the same hardware.
When you’re paying for managed hosting, you should be getting the performance the platform is actually capable of, not what it could do six years ago.
The practical result for WordPress 7.0: the PHP requirement change doesn’t affect a single one of our maintenance customers. We’ve been ready for this for a long time.
Our rollout plan
Here’s how we’re handling WordPress 7.0 across the maintenance portfolio:
This week
Every maintenance site gets a fresh staging clone if it doesn’t already have one. We’re running WordPress 7.0 against those staging environments first. Plugin compatibility checks, theme rendering passes, and full admin walkthroughs against the new DataViews screens.
Every staged deployment also includes verified backups and rollback procedures before production updates begin.
Next one to two weeks
We sit with the staging results and let the WordPress community surface the issues that always come out in the first week or two after a major release. A 7.0.1 patch is almost certainly coming. We’d rather deploy that than 7.0 vanilla.
Once we’re confident
Production updates roll out in tiers. Low-complexity sites (basic WordPress, well-maintained themes, common plugin stacks) go first.
Complex sites with custom development, WooCommerce, membership systems, or unusual plugin combinations get extended testing and a scheduled maintenance window.
You’ll get a heads up before your site is updated. If anything looks risky on your specific stack, we’ll reach out and walk through the options.
Why this matters for business owners
Major WordPress updates can impact ecommerce functionality, payment systems, lead generation forms, SEO plugins, memberships, custom integrations, and business-critical workflows.
A rushed update can easily turn into downtime or lost revenue if compatibility issues are missed.
That’s why staging, testing, backups, rollback planning, and controlled rollout processes matter.
If you’re not a maintenance customer
This is the kind of release where DIY updates bite people.
If you’re running WordPress on shared hosting somewhere and you’ve been meaning to get a proper maintenance plan in place, WordPress 7.0 is a reasonable nudge.
Worst case, you click update and something breaks at 9pm on a Friday.
Best case, you spend the weekend reading forum posts trying to figure out what changed.
We handle the whole thing. Staging, testing, plugin compatibility, the actual update window, verified backups, and the rollback plan if something goes sideways.
If you want to talk through what that looks like for your site, get in touch.
For now, sit tight. We’ve got it.
