WordPress releases a few major versions a year, plus regular maintenance and security releases. The next major release, WordPress 7.2, is scheduled for 8 December 2026, with its first release candidate on 17 November. It's described as the final major release of 2026.

Major releases bring new features and improvements, but on business sites with many plugins, updating carelessly can break layouts, forms or checkouts. Here's a safe process.

Major vs minor updates

TypeExampleWhat to do
Minor (security and maintenance)7.1.3Apply promptly; usually installs automatically
Major7.2Test on staging, then update deliberately
Plugin and theme updatesVariesTest important ones; update regularly
PHP versionServer levelPlan and test; affects everything

Before the release: get ready

  1. Check your current setup: WordPress version, PHP version, theme, plugins and when they were last updated.
  2. Remove unused plugins and themes. Each one is a risk.
  3. Check plugin support: look at plugin changelogs and support pages for compatibility notes on the new version.
  4. Make sure you have a staging site, a private copy for testing. Many hosts offer one-click staging.
  5. Confirm backups work by restoring one to staging. Read website backup strategy.

The update checklist

Step 1: Full backup

Back up files and database, stored off the server. Note the time so you know what to restore.

Step 2: Update staging first

Copy the live site to staging, then on staging:

  1. Update plugins and the theme to their latest versions.
  2. Update WordPress core to the new version.
  3. Check for errors in the dashboard and the PHP error log.

Step 3: Test what matters

AreaWhat to check
Key pagesHome, services, products, about, contact: layout and content
FormsSubmit every important form; confirm emails arrive
E-commerceAdd to basket, checkout with a test payment, order emails
LoginsAdmin and customer accounts
EditorEditing and publishing pages in the block editor or page builder
IntegrationsCRM, email marketing, analytics, payment gateways
SpeedCompare page speed with before. See INP explained
SEOTitles, meta descriptions, sitemap and robots.txt still correct
MobileCheck key pages on a phone

Our free sitemap validator, robots.txt tester and broken link checker speed up the SEO checks.

Step 4: Fix or wait

If something breaks, check whether a plugin update fixes it, contact the plugin developer or wait for a patch. Don't update live until staging works.

Step 5: Update live at a quiet time

Choose a low-traffic time. Back up again, then apply the same updates in the same order. For shops, avoid peak periods such as the run-up to Christmas, or update before the busiest weeks begin.

Step 6: Test live straight away

Repeat the key checks: pages, forms, checkout, logins.

Step 7: Monitor for a week

Watch error logs, uptime, form submissions, orders and Search Console. Some problems only appear with real traffic.

Plugins and setups most likely to cause trouble

Not all plugins carry the same risk during a major update. Give these extra testing time:

TypeWhy it's risky
Page buildersDeeply tied to the editor and front-end rendering
E-commerce plugins and their extensionsCheckout, payments and emails must keep working
Caching and performance pluginsCan serve old or broken pages after changes
Security and firewall pluginsCan block admin actions or updates
Membership and LMS pluginsComplex logins, permissions and payments
Custom or abandoned pluginsNobody may be updating them for new versions
Heavily customised themesCustom code may rely on behaviour that changed

Plugins that haven't been updated in over a year are a warning sign for compatibility and security. Look for maintained alternatives.

A simple update log

Keep a short record each time you update:

DateWhat was updatedTested byIssuesBackup reference
9 Dec 2026Core 7.2, WooCommerce, themeStaging + live checksMinor layout fix on blog pageBackup 9 Dec 06:00

It makes troubleshooting much faster when something surfaces weeks later.

Rolling back

If the live site breaks and you can't fix it quickly:

  1. Put up a maintenance message if needed.
  2. Restore the pre-update backup.
  3. Investigate on staging.

WordPress's recovery mode emails the site admin when a fatal error occurs, with a link to disable the faulty plugin or theme.

Keep up between major releases

Regular maintenance makes major updates painless:

  • Apply security releases promptly.
  • Update plugins and themes at least monthly.
  • Keep PHP on a supported version.
  • Review plugins quarterly and remove what you don't need.
  • Monitor uptime, broken links and SEO issues. Zelvorm Watch keeps checking for broken links, SEO faults and spam pages.

Our WordPress maintenance checklist covers the routine in detail.

When WordPress becomes a burden

If updates constantly break your site or you're running dozens of plugins to get basic features, it may be time to rethink. Read how often you should update your website, 12 signs your website needs a redesign and Next.js vs WordPress.

The short version

WordPress 7.2 is due on 8 December 2026. Before any major update, back up, remove unused plugins, check compatibility and test everything on staging: pages, forms, checkout, logins, integrations, speed and SEO. Update live at a quiet time, test again and monitor for a week, with a tested backup ready to roll back.

Prefer someone else to handle updates? Our maintenance and support team keeps WordPress sites updated, backed up and monitored.