← All articles Troubleshooting

WordPress 7.2: What to Do Before the December Release

WordPress 7.2 is scheduled for final release on 8 December 2026. If your site takes orders, captures leads, or manages customer accounts, that date is a

Published Jason Boyd

WordPress 7.2 is scheduled for final release on 8 December 2026. If your site takes orders, captures leads, or manages customer accounts, that date is a deadline to plan around now, not a feature announcement to skim and forget.

Major WordPress releases follow a public development cycle. Release Candidate 1 marks the point where the codebase is considered feature-complete and enters final testing, which means the architecture of 7.2 is already fixed. Plugin and theme developers have had access to test against it, but many smaller or less actively maintained plugins will not have been tested at all. The gap between “the release is out” and “everything works as it did before” is where business owners get into trouble.

The risk is concrete. Applying a major WordPress update directly to a live site without prior testing can take down a checkout flow, break a contact form, or corrupt session handling on a membership site, and none of those outcomes require a dramatic failure. A single incompatible plugin can be enough to render a page blank, throw a fatal error on checkout, or silently stop form submissions from reaching your inbox.

The Three Things to Arrange Before 8 December

Confirm your backups are current and tested. Before any major update, verify that your most recent backup is complete, that it includes both the database and all site files, and that you or your developer can actually restore from it. Automated backup plugins can silently fail if storage limits are hit or authentication tokens expire, so check the last successful backup timestamp rather than whether the plugin is simply active. A backup you cannot restore from is not a backup.

Check plugin compatibility before update day. Log into your WordPress dashboard and make a list of every active plugin. For each one, check the plugin’s page on the WordPress plugin directory and look at the “Tested up to” field. If a plugin you depend on for payments, bookings, or lead capture has not been tested against WordPress 7.2, contact the developer or check their changelog before the release date. Do not assume silence means compatibility.

Test on a staging environment, before you touch the live site. A staging environment is a private copy of your site where you can apply updates, break things, and fix them without affecting a single real visitor or transaction. Most managed hosting providers offer one-click staging; if yours does not, this is worth raising with your developer before December. Run the 7.2 update on staging first, click through every critical journey (checkout, enquiry form, login, account page), and only push to live once you have confirmed everything works.

These three steps take time to arrange if you are not already set up for them, which is the reason to start now rather than the week before release.

Why Waiting Until Release Day Puts Trading Operations at Risk

On release day, a wave of sites update automatically or are updated by owners who assume the process is safe. Within 24 to 48 hours, support forums fill with reports of broken sites, plugin developers push patches, and hosting companies field support tickets. If your site is one of those affected, you are competing for developer attention at the worst possible moment whilst your checkout is down or your enquiry form is silently discarding submissions.

Automatic updates make this worse. WordPress can be configured to apply major releases automatically, and some hosting environments enable this by default. If you are not certain whether your site has automatic major updates enabled, check under Settings > General or ask your developer. An unexpected major update applied overnight, with no staging test and no confirmed backup, is the scenario that causes the most damage.

The businesses most exposed are those running WooCommerce alongside a stack of payment, shipping, or CRM plugins. A WooCommerce store typically has more plugin dependencies than a brochure site, and each one is a potential point of failure after a major core update. The checkout page alone may depend on WooCommerce itself, a payment gateway plugin, a tax calculation plugin, and a shipping rate plugin, all of which need to be compatible with 7.2 before you update.

Customer data integrity is the angle most business owners miss until it is too late. A failed update that leaves your database in a partially migrated state can cause order records to display incorrectly, membership access to drop, or customer account data to become inaccessible. Restoring from backup fixes the site, but any orders or form submissions captured between the failed update and the restore point are gone. For a site processing even a modest volume of daily enquiries or transactions, that is real commercial loss.

If you are running a WordPress site that handles any kind of commercial activity without a tested backup, a staging environment, and a plugin compatibility check in place before 8 December, that is an open risk on your business right now.

I offer a pre-update audit at The WordPress Guy specifically for situations like this: a full compatibility check across your plugin stack, a staging environment test of the 7.2 update, and a confirmed backup before the release date arrives. With 8 December approaching and developer time filling up, the window to arrange this before the release is shorter than it looks.

Book the pre-update audit before the release date closes the window.

Related articles

All articles →

Intermittent errors and unexplained failures are my speciality. If this sounds like your site, I can diagnose it properly.

View troubleshooting services →
Jason Boyd

Jason Boyd

Specialist WordPress Engineer · Former W3C Invited Expert · 20+ years

I fix the WordPress problems other developers walk away from. Backed by a 1st Class degree in Computer Science, an MSc in Cybersecurity, and over 20 years of specialist WordPress work, I diagnose issues at their root cause and resolve them permanently, for businesses that cannot afford guesswork or repeat failures.

Need hands-on help?

If this article describes your situation, I can diagnose the specifics and fix it properly. Send your brief and I'll respond the same working day.