WordPress 7.0 releases on May 20. Your hosting provider will send you a notification. The dashboard banner will appear. Every WordPress blog will publish some version of “What’s New in 7.0 — Update Now.” Don’t. Not on day one. Not on a live production site.
What’s Actually New in 7.0 (And Why the Timing Still Matters)
WordPress 7.0 is a genuine step forward. The block editor gets meaningful improvements, layout classes work correctly now, and the real-time collaboration work — though it didn’t ship in this release — pushed the codebase in good directions. The core team delivered clean, well-tested code. That’s not the problem. The problem is everything built on top of it.
The 72-Hour Plugin Gap Nobody Talks About
When a major WordPress version ships, plugin authors are racing to catch up. On release day, compatibility gaps are everywhere. A contact form plugin that worked perfectly yesterday throws a fatal error today. A WooCommerce payment extension silently breaks on checkout. A page builder that powers your entire site layout renders blank. This isn’t a WordPress failure — it’s just how an ecosystem of thousands of independent plugins works at scale. The core ships on schedule. The compatibility window takes 7–14 days to close.
The 3-Step Update Process That Keeps Sites Safe
Here’s what actually works: first, update your staging site on release day if you want to see what changed — that’s what staging is for. Second, spend a few minutes in your plugin list checking which ones haven’t been updated for 7.0 compatibility yet; your dashboard will flag this, and plugin changelogs will tell you whether the author has acknowledged the new version. Third, wait two weeks before touching production. By then, the major plugin authors have pushed compatibility updates, community bug reports have surfaced any real issues, and you can update with confidence instead of crossing your fingers. One client ignored this advice on a 6.5 release day — a WooCommerce extension broke mid-afternoon and took down their checkout for three hours on a Tuesday.
How do you handle major WordPress updates — do you update immediately, wait it out, or hand it off entirely? Curious what’s worked for other developers and site owners. Reach out to @noma_digital on X.