Applying WordPress Major Updates Safely – 7.0 "Armstrong"
A major update is a different thing from a small security update. It brings new features and deeper changes – and with them a higher risk that a plugin or theme won’t immediately play along. A current example: WordPress 7.0 “Armstrong”, released on 20 May 2026, with a revamped editor, performance improvements and a modernised REST API. The following method applies to every major release.
Before: Clarify Three Things
- Backup of files and database – fresh, not from last week. It’s your return ticket if something snags.
- Check compatibility: are the theme and key plugins cleared for the new version? For major plugins, that’s usually stated promptly in the release notes. Extensions that are no longer actively maintained deserve special attention – they’re the most common reason a major update trips up.
- Check the PHP requirement: major releases often require a current PHP version – a good occasion to update the PHP version at the same time.
The Safe Process via Staging
Never apply a major update blindly on the live site. Instead:
- Apply the update on a staging copy.
- Click through: home page, key subpages, forms, and for shops the complete checkout. Watch for layout breaks and broken functionality.
- If problems appear: update or replace the affected plugins/themes, only then continue.
- If all works, apply the update to live in a controlled way – ideally outside peak hours.
- Then verify live and keep an eye on error messages for a day.
Update Immediately or Wait a Little?
Applying a major update live in the first hours after release is unnecessarily risky – the plugin makers also need a moment to confirm their compatibility and ship the first follow-up patches (7.0.1, 7.0.2). Waiting one to two weeks and testing via staging in that time is the pragmatic middle ground between “immediately” and “not at all”.
When Something Stalls During the Update
If an update breaks off and the site shows “Briefly unavailable for scheduled maintenance”, usually just one file is to blame → fix the maintenance mode. If instead of the maintenance screen a critical error appears, that points to a PHP error – find the diagnostic entry point there. Stalls like these are exactly why major updates shouldn’t be applied on the side. Because you tested via staging, in the best case they happen there and not in front of your visitors.
Why Not to Wait Forever
Postponing major updates feels safe but isn’t: at some point the old version drops out of security support, and the jump grows bigger and riskier with every skipped release. Updating promptly in a controlled, tested way is safer than the big catch-up jump in two years – and exactly this prompt, tested updating is part of any good WordPress maintenance.
A major update coming up and you want it applied without risk? Drop us a line – we test via staging and bring you cleanly onto the new version.
Frequently Asked Questions
What is a WordPress major update?
A major update is a large version jump like from 6.x to 7.0, as opposed to a small minor or security update. It brings new features and deeper technical changes – and with them a higher risk that a plugin or theme won't immediately play along. That's why a major update belongs prepared and tested, not just clicked away in the backend.
How do I apply a major update like WordPress 7.0 safely?
First a fresh backup, then check the compatibility of the theme and key plugins and the PHP requirement. Then apply the update on a staging copy and click through the central pages, forms and, for shops, the checkout. Only when everything works there do you repeat the update on live in a controlled way – ideally outside peak hours and with an eye on error messages.
Should I update to a major release immediately?
Not in the first hours, but also not for months on end. A sensible approach is to wait one to two weeks, until the most important plugins have confirmed their compatibility and the first follow-up patches have appeared – and then to update in a tested way. Postponing forever is more dangerous, because the old version eventually drops out of security support and the jump grows with every skipped release.
What do I do if a major update breaks a plugin?
If you tested via staging, you notice it there and not on the live site. Then update the affected extension, replace it with a maintained alternative, or temporarily deactivate it – and only then go live. If it did happen on live, the backup helps you revert to the old version until the cause is clear.
Related Services
Founder & Full-Stack Developer
20+ years of web development experience. Specialised in Laravel, WordPress and custom software for mid-sized businesses.