WordPress 7.0: The Great Purge and the dawn of the Collaboration Era

I know, I know – the title is pretty grandiose. Almost epic sounding. But it really is a big deal.

The transition from WordPress 6.x to 7.0 isn’t a typical incremental update. It’s a fundamental restructuring of how the world’s most popular CMS functions. For the last few years, the era of Phase 2, the community has been focused on the transition to the Block Editor. It was often messy and fragmented. We’ve seen “hybrid” sites that tried to keep one foot in the classic world and one in the block world. WordPress 7.0 is the moment the platform finally stops looking over its shoulder.

It’s a “clean slate” release. This aligns perfectly with our quality-first philosophy. We’ve always believed that commercial outcomes are built on a foundation of high coding standards, and version 7.0 effectively makes those standards mandatory. If your site has been held together by legacy hacks and “good enough” plugins, 20 May 2026 is going to be a day of reckoning.

The Technical Floor: A New Standard for Stability

For developers, 7.0 is an ultimatum. It’s the final push into a modern, JavaScript-heavy, and API-driven architecture. The first thing every stakeholder needs to check is the server floor. WordPress 7.0 officially leaves PHP 7.2 and 7.3 in the rearview mirror. While the platform has technically supported these versions for far too long, version 7.0 mandates PHP 7.4 at an absolute minimum. However, for a quality-led build, we’re looking at PHP 8.3 as the target.

It’s not just PHP. The requirement for MySQL 8.0 is a significant jump. This isn’t just about security, it’s about the performance required to handle the real-time data syncing that 7.0 demands. If you’re managing sites on budget hosting environments that are still running MySQL 5.7, those sites are now officially technical debt. They won’t receive the update, and they’ll be stuck on the 6.9 legacy branch, missing out on every major productivity feature of the next decade.

The Iframe Shift and the End of DOM Hacks

Perhaps the most significant “under the hood” change for developers is that the Post Editor is now always iframed. In previous versions, the editor shared the same DOM (Document Object Model) as the rest of the WordPress admin. This allowed developers to write lazy scripts that targeted the “document” or “window” objects to force changes in the editor.

That door is now closed. Because the editor is in its own iframe, those scripts will fail. If you’ve built custom editor tweaks that aren’t using the proper Block API or the wp.data store-they will simply vanish. This change ensures that the editor’s CSS and JavaScript are perfectly isolated-preventing the “leaking” styles that have plagued custom dashboard builds for years. It’s a win for stability, but it’s a nightmare for anyone who hasn’t been following block-standardised development practices.

The Meta Box Conflict

We need to talk about the “Collaboration Killer.” WordPress 7.0 introduces real-time co-editing. But there’s a catch. If the system detects a “Classic Meta Box” – those old PHP-rendered fields at the bottom of the editor – it will disable collaboration features for that post type.

For years, developers have relied on plugins like ACF (Advanced Custom Fields) or custom PHP hooks to add metadata. If those fields aren’t registered using the modern REST API or converted into “Plugin Sidebar” components, the site’s users lose the headline feature of 7.0. It creates a direct friction point between developers who want to stick to old methods and marketing teams who want modern tools. At Step3, we see this as a necessary push toward the Block API, ensuring that the data layer and the UI layer are finally speaking the same language.

DataViews: The New Admin Framework

The traditional PHP-rendered tables we’ve used to manage “All Posts” or “All Pages” are being phased out in favour of DataViews. This is a new, high-performance UI framework based on React.

For developers, this means the end of the WP_List_Table class as we know it. If you’ve built custom dashboards or complicated filtering systems for e-commerce clients, you’re going to have to refactor those views into the DataViews API. It’s a shift from server-side rendering to client-side interaction. It makes the admin feel like a modern web app, but it requires a level of JavaScript proficiency that many legacy WordPress developers simply haven’t modernised into yet.

What this means for Website Owners and Marketing Departments

For the average website owner or marketing manager, WordPress 7.0 is the most “human” update we’ve seen. It moves away from technical jargon and focuses on the actual experience of running a digital brand.

The End of the Content Bottleneck

The most immediate change you’ll notice is the removal of the “Lock” screen. For a decade, if your SEO specialist was tweaking a meta description, your content writer couldn’t edit the headline. It was a linear, clunky, and frustrating process.

WordPress 7.0 introduces Real-Time Collaboration. You can now have a designer working on the layout, a copywriter refining the prose, and a marketing manager leaving feedback. All at the same time. You’ll see live cursors moving across the screen, just like in Figma or Google Docs. This isn’t just a “nice to have”, it’s a massive efficiency gain. It cuts down the feedback loop from hours to minutes.

Fragment-Level Feedback

Following the collaboration theme, the new Commenting API allows for “Fragment-Level” notes. Instead of sending a Slack message saying “The third paragraph on the home page needs more punch”, you can simply highlight that specific sentence in the WordPress editor and @mention your colleague.

They receive a notification, can reply, or can “resolve” the comment once the change is made. This keeps the entire editorial conversation inside the website itself. It reduces the chance of “lost in translation” errors and ensures that the context of the change is never lost. For busy marketing departments, this is the end of the messy email trail and the “who said what” confusion.

High-Speed Workflows: Browser-Side Processing

We’ve all been there: you’re trying to upload a 5MB hero image, and the server chokes or the upload takes forever. WordPress 7.0 solves this with Browser-Side Image Processing.

When you drag an image into the editor, it is now resized and converted to WebP or AVIF on your computer before it even starts uploading to the server. This means:

• Uploads are significantly faster because the file size is smaller before the transfer begins.
• Your server doesn’t have to work as hard-lowering your hosting overhead.
• Your site stays fast for visitors because every image is automatically optimised by default – without the need for extra image compression plugins.

It’s a “Show, Don’t Tell” feature. You won’t see a complex settings page, you’ll just notice that your media library feels lighter and more responsive.

Native Responsive Controls

WordPress 7.0 brings Native Responsive Controls to every block. You can now toggle visibility based on device type directly in the sidebar. This gives marketing teams granular control over the mobile experience without needing to call a developer for every minor tweak. It’s about empowering the people who use the site every day, while ensuring the underlying code remains clean and performant.

The Commercial Reality of Technical Debt

Here is the uncomfortable truth: WordPress 7.0 is going to break some sites. If your website was built five years ago on a cheap theme with a handful of random plugins, you are going to see some issues.

The move to PHP 7.4/8.3 and MySQL 8.0 means that some older hosting setups will simply stop working. This is actually a good thing. It forces a conversation about Digital Hygiene. For a business – your website is a commercial asset. If that asset is built on crumbling foundations – it’s a risk. WordPress 7.0 makes that risk visible. It rewards those who invest in quality-standardised builds and provides a clear path forward for those who want to build a modern, scalable, and collaborative digital presence.

At Step3, we aren’t just “updating” sites. We’re using this release to audit everything. We’re looking for legacy meta boxes that will block the new collaboration features and outdated hosting that doesn’t meet the new MySQL 8.0 requirements.

Our approach is, as always, quality-first. We recommend a “Wait and Audit” strategy. Don’t rush into the 7.0 update on day one. Instead, run a staging environment, test your custom functionality, and ensure your team is trained on the new collaboration tools. WordPress 7.0 is the future of the web, and for those who build with standards in mind, the future looks very bright indeed.

Are you worried about how your current site will handle the jump to 7.0? Let’s talk about a quality audit.