Introduction
On May 20, 2026, WordPress 7.0, codenamed «Armstrong,» was released — the biggest core release in years. Two months later, on July 17, 7.0.2, an urgent security update, was released. If you manage an eShop or site on WordPress, it’s worth knowing what’s changed and why you shouldn’t leave the upgrade for «someday.».
Artificial intelligence at the core
The big news of 7.0 is that AI is officially entering the core of WordPress. The core gets a AI Client provider-independent, an expanded Abilities API and a new screen Settings > Connectors from where you connect with a few clicks to Anthropic, Google or OpenAI.
In practice, this means that plugins and themes can now «talk» to AI models in a common, standardized way — without each plugin having to set up its own connection. The optional official AI plugin adds ready-made functionality: image creation and editing, automatic titles and summaries, and even alt text suggestions.
What does it mean to you: The infrastructure is built into the core, but the AI doesn’t activate itself. Nothing is sent to third parties unless you connect a provider. This is important for GDPR — and all the more reason to know exactly what’s active on your site.
Renewed management environment
The admin dashboard gets a long-awaited refresh with the new Modern admin theme. Many areas are being improved: the admin headers, the Customizer, the color picker, the script loader, and the user registration screens in multisite.
It stands out Command Palette: an icon in the top bar (⌘K on Mac, Ctrl+K on Windows) that opens a command prompt from anywhere in the dashboard. You type and jump straight to pages, settings, or actions — without digging through menus. For anyone who works in WordPress every day, it’s a real time saver.
Content editor improvements
The block editor is getting tools that the community has long requested.
Visual Revisions: You can now visually compare two versions of a page within the editor itself, with a slider bar that toggles between the two snapshots. No more guessing what changed between revisions.
Responsive controls: settings are added that allow you to decide whether a specific block is shown or hidden per device type — directly from the editor, without custom CSS.
New blocks: Headings, Icons, and Breadcrumbs are coming to the core, along with lightbox support in Gallery blocks and dynamic URLs in Navigation Link blocks.
What was cut — and what to watch out for
Η real-time collaboration, i.e. simultaneous editing of multiple users in real time, was removed from the version shortly before the release, on May 8, due to stability issues (race conditions and server load). It will return in a future version, not now.
The most practical point for compatibility: the minimum PHP becomes 7.4 and support for PHP 7.2 and 7.3 is ending. If your site is still running on an old version of PHP, you will need to upgrade your environment before moving to WordPress 7.0.
Two months later, 7.0.2
On July 17, 2026, WordPress 7.0.2 was released, a purely security release. It fixes two vulnerabilities: one critical and one high severity.
This is an SQL injection issue and a confusion in the batch routes of the REST API which, combined, could lead to remote code execution (Remote Code Execution) — that is, in the worst case, complete control of the site by an attacker. This is not a theoretical risk; the official recommendation is to update immediately.
The fact that such a major feature release needed a security patch within two months isn't a bad sign — on the contrary, it shows that the WordPress team is monitoring and quickly closing the loopholes. The question is, will your site have time to implement them?.
What to do now?
The correct order for an upgrade of this size is not to blindly press the "Update" button:
1. Keep a full backup (files and database) before touching anything.
2. Check the server's PHP version — you need at least 7.4, ideally something much newer.
3. Try upgrading to staging, not directly to live, especially if you have WooCommerce and custom plugins.
4. Check theme and plugin compatibility with 7.0 before releasing it to production.
5. Once you're sure, go straight to 7.0.2 to also cover the security gap.
If all of this sounds like a lot to take on alone — especially when safety is a concern — that's exactly what we do every day at Fixit. We undertake the upgrade in a controlled manner, in staging, with backups and testing, so that your site is on the latest and secure version without surprises.