Blog
SavedSearch
Visit Hostlelo

WordPress 7.2 lands 8 December: your 18-day readiness plan

WordPress 7.2 is planned for 8 December 2026. Use the release candidate weeks to test a copy of your site, check PHP, and line up a backup and rollback.

The short answer

WordPress 7.2 is planned for release on 8 December 2026, and release candidates are already available for testing. The safe plan is to copy your site, update the copy to the newest release candidate with the Beta Tester plugin or WP-CLI, test logins, forms, checkout, admin screens, media uploads and custom code, and fix problems before release day. Take a full database and file backup before updating the live site, because a rollback needs the backup from before the update.

Developer testing a WordPress staging site with a checklist, backup and calendar
Reading options

On this page

Before you start

Use a staging copy that cannot send real email or charge real payments. Before testing, keep a verified database dump and a separate files/configuration backup outside the public web directory and copy both off-server. Install release candidates only on non-production systems.

WordPress 7.2 is planned for 8 December 2026. As of 20 November, the official project page is in the release-candidate phase, leaving 18 days to test a copy of your site before the planned final release. A release candidate (RC) is still pre-release software published so people can find the last bugs.

The RC1 announcement says plainly: "Please do not install, run, or test this version of WordPress on production or mission-critical websites." Keep this work on a copy, and leave the live site on the current stable release until your own tests pass.

By the end of this post you will have a dated plan, a test checklist you can run in under an hour, the WP-CLI commands for backup and update, and a clear rollback rule.

What a WordPress readiness plan actually is

A readiness plan is a short list of checks you run on a copy of your site before a major update reaches the real one. Think of it like a dress rehearsal before a wedding. Nobody wants to find out the microphone is broken while the guests are already seated.

WordPress 7.2 is a major release, which means new features and changed code, unlike a small security release. At the time of review (20 November 2026), the RC1 announcement lists these highlights among others: a new default theme called Ipsum, faster media uploads and image processing, a modernised admin with SVG icons, faster admin navigation, and "Accessibility, security, and PHP 8.6 compatibility improvements".

Why this matters: every change that helps most sites can still trip one plugin or one piece of custom code. Your job is to find out whether that one is yours.

One quick note before the plan. WordPress 7.1.5 came out on 18 November 2026 as a security release, and the team recommends updating immediately. Its fixes include an unauthenticated privilege escalation through Template Part block attributes that could lead to remote code execution, SQL injection in WP_Meta_Query, several XSS issues, and a denial of service through batched XML-RPC pingbacks. Put your live site on 7.1.5 today, using the steps in our 7.1.x security update checklist, and then come back to this plan. The same post confirms that 7.2 RC2 was released with all applicable fixes.

Before you start

Gather these before you touch anything. Most of it takes ten minutes.

  • Admin login to your live WordPress site.
  • Access to your hosting control panel or SSH, so you can create a copy and take backups.
  • WP-CLI on the server if you want the command line route (WP-CLI is the official command line tool for WordPress).
  • A list of the plugins and theme your site truly depends on, plus any custom code a developer wrote for you.
  • A place to store backups that is not the same folder as the site.
  • Time: about one hour per test cycle before release.
  • Risk level: low on the copy, because nothing there touches real visitors. The only risky moment is the live update on or after 8 December, and the backup step covers that.

Heads up: the copy must not send real emails or take real payments. Switch your payment gateway to its test or sandbox mode on the copy, and stop it from emailing real customers if your plugins allow that.

The 18-day plan, with dates

The official 7.2 project page currently shows the final release planned for 8 December 2026, with further release-candidate work on 24 November and 1 December, then a dry run and 24-hour code freeze on 7 December. Separate official planning pages do not label every RC date consistently, so use the newest build linked by WordPress.org rather than assuming an RC number from a calendar.

The schedule can move. Check the WordPress 7.2 project page and the latest WordPress.org News announcement before every test cycle.

Week 1 (20 to 26 November): make the copy and test the newest RC

Create a test copy of your site. Many hosts have a staging tool in their control panel, and the exact clicks differ by host and panel, so follow your host's own guide for that part. I have not verified any panel's staging steps for this post. WordPress.org also announced a free tool called Reprint on 13 November 2026, which can copy a site's files and database and is described as useful for "a site copy meant for testing".

Then update the copy to the newest release candidate linked by WordPress.org. Run the checklist below once this week and write down the exact version and anything that breaks.

Week 2 (27 November to 3 December): fix, update plugins, retest

Ask plugin and theme vendors about anything that broke. Plugin authors have been asked to finish testing and set "Tested up to" to 7.2 in their readme, so it is fair to ask whether they have. After the next release candidate is published, update the copy again and rerun the checklist.

Week 3 (4 to 8 December): freeze, back up, decide

Stop making changes to the live site from about 4 December, so the copy and the live site stay close. On release day, take a fresh backup, then update the live site only if your copy passed. If anything is still red, it is perfectly fine to wait a few days and stay on 7.1.5 while you sort it out. Our post on controlling the WordPress update window explains how to keep updates on your schedule.

How to put the copy on the latest release candidate

You have two official routes. Pick one.

Option A: the WordPress Beta Tester plugin

This is the easiest route if you prefer clicking. Install and activate the WordPress Beta Tester plugin on the copy only, then go to Tools > Beta Testing. On Multisite, it lives under Settings > Beta Testing instead.

Choose the Bleeding edge channel and the Beta/RC Only stream, as the RC1 announcement describes. Save, then go to Dashboard > Updates and update. The plugin page also reminds you: "Don't forget to backup before you start!"

Quick tip: after you update, check the version number the plugin shows against the latest announcement on WordPress.org News, so you know which RC you are testing.

Option B: WP-CLI

First, back up the copy's database outside its public web directory. This unexecuted example creates a private directory under the account home, uses a unique UTC timestamp, verifies the dump is non-empty, and prints the exact path. It is a database-only backup; keep a separate verified copy of wp-content, wp-config.php and any server rules.

set -eu
umask 077
backup_dir="$HOME/private-backups"
mkdir -p "$backup_dir"
backup="$backup_dir/wordpress-7-2-rc-$(date -u +%Y%m%dT%H%M%SZ)-$$.sql"
wp db export "$backup"
test -s "$backup"
ls -lh "$backup"

Copy both the database dump and the file backup to protected off-server storage. Then check which version the copy is on now.

wp core version

The RC1 announcement published this exact command on 17 November. It is a dated, unexecuted example, not a promise that RC1 is still the newest build.

wp core update --version=7.2-RC1

Before running a CLI update, open the latest WordPress.org News release-candidate announcement and replace 7.2-RC1 with the exact version it names. The --version option targets one specific version. If you do not want to manage RC numbers manually, use the Beta Tester plugin's Beta/RC Only stream on staging instead.

Heads up: the WP-CLI page for wp core update gives no rollback procedure. On the copy, your reset button is the backup you just took.

The one-hour test checklist

Run this on the copy after each RC update. Log in in a private browser window so cached sessions do not hide problems.

  1. Log in and log out. Try a password reset if your users rely on it.
  2. Submit every important form: contact, quote request, sign-up.
  3. If you sell things, run one full checkout in test mode, from cart to the thank-you page and the order email.
  4. Open the admin screens you use daily: posts, pages, the editor, menus, your shop or booking screens.
  5. Edit and save one post in the block editor, and preview a revision.
  6. Upload a JPEG and a PNG from Chrome, then again from Firefox or Safari, and check the image sizes look right in the Media Library.
  7. Click through each plugin that matters to your business and use its main feature once.
  8. Test any custom code: theme functions, custom blocks, shortcodes, scheduled tasks.
  9. Check the front end on a phone.
  10. Read the PHP error log and the browser console for new errors.

Why step 6 matters: WordPress 7.2 extends client-side image processing to the Media Library grid, the Add New Media File screen and the media modal. The media dev note says this currently needs Chromium 137 or newer, and that Firefox and Safari uploads use the classic server-side path. So the same upload can take two different paths depending on the browser, and you want both tested.

Made-up example: Sara runs a small bakery site with a booking form and a shop. On her copy, everything passes except the booking plugin's calendar, which throws a JavaScript error in the admin. She sends the error to the plugin vendor in week 1, installs their fix in week 2, and updates the live site calmly on 9 December. Sara and her bakery are invented for this post, but the order of events is exactly the point.

Check your PHP and database versions now

At the time of writing (19 November 2026), the WordPress requirements page recommends PHP 8.3 or greater, MariaDB 10.11 or greater or MySQL 8.4 or greater, and HTTPS support. PHP.net lists security support for PHP 8.2 ending on 31 December 2026, three weeks after 7.2 ships.

To see what your site actually runs, open Tools > Site Health > Info in the WordPress admin and look at the Server and Database sections. On the command line, this prints details about the WP-CLI environment, including a PHP version line.

wp cli info

Heads up: the PHP version that WP-CLI uses on the command line can differ from the one serving your website, so trust Site Health for the web side. If you are on 8.2 or older, plan the PHP move separately from the WordPress update, so that if something breaks you know which change caused it. Our PHP 8.2 end of security support guide walks through that upgrade.

How to check it worked

After updating the copy, and later the live site, run these checks.

This prints the installed version. On the copy it should show the RC you installed, and on the live site after release day it should show the final 7.2 version.

wp core version --extra

This lists active plugins with their versions and whether an update is waiting, so you can confirm nothing got deactivated during the update.

wp plugin list --status=active

On the live site after the final release, this compares your core files with the official checksums from WordPress.org. You should see Success: WordPress installation verifies against checksums. Our guide to verifying WordPress files with WP-CLI checksums explains what to do if it warns about a file.

wp core verify-checksums

In the browser, load the home page, one post, one product or booking page, and the admin dashboard. Check Tools > Site Health > Status for any new critical items.

Troubleshooting

Problem: the copy shows an older RC than the one just announced

Symptom: wp core version shows an older RC after WordPress.org publishes a newer one. Cause: a dated --version command pins that exact build. Fix: use the version in the latest official announcement, or switch the staging copy to the Beta Tester plugin's Beta/RC Only stream, then record the version shown after updating.

Problem: a white screen or "critical error" after updating the copy

Symptom: the site or admin stops loading. Likely cause: a plugin or theme function that does not work with the new code. Fix: on the copy, turn on debug logging in wp-config.php so errors go to a file instead of the screen. The official debugging guide gives these lines.

// Enable WP_DEBUG mode
define( 'WP_DEBUG', true );

// Enable Debug logging to the /wp-content/debug.log file
define( 'WP_DEBUG_LOG', true );

// Disable display of errors and warnings
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );

Reload the page, then read wp-content/debug.log. The file name and plugin folder in the error usually point to the culprit. The same guide says it "is not recommended to use WP_DEBUG or the other debug tools on live sites," so keep this on the copy.

Problem: JavaScript errors in the admin from an older plugin

Symptom: buttons that do nothing, or red errors in the browser console on a plugin's settings page. Likely cause: old jQuery code. WordPress 7.2 ships jQuery Migrate 3.6.0, which the dev note says will "help extenders catch deprecation notices in their code." Fix: on the copy, add define( 'SCRIPT_DEBUG', true ); to wp-config.php so WordPress loads the readable "dev" versions of core CSS and JavaScript, reproduce the problem, and send the console message to the plugin author.

Problem: image uploads behave differently in Chrome and Firefox

Symptom: uploads from Chrome create animated sub-sizes or slightly different files than uploads from Firefox or Safari. Cause: client-side processing runs only in supported Chromium browsers, and other browsers use the classic async-upload.php path. Fix: if this causes trouble for your workflow, the media dev note gives a filter to turn client-side processing off. Put it in a small custom plugin or your theme's functions file.

add_filter( 'wp_client_side_media_processing_enabled', '__return_false' );

If only animated GIFs and WebPs are the issue, the note offers a narrower filter that keeps client-side processing but generates static sub-sizes for animated images.

add_filter( 'wp_generate_animated_image_subsizes', '__return_false' );

Problem: multisite uploads fail or miss image sizes

Symptom: on a network with "Site upload space" enabled, some uploads fail or only some thumbnail sizes appear. Cause: the media dev note says each generated sub-size is now checked against the quota, and missing sizes are not reported to the user. Fix: raise the site's upload quota or clear old media on sites close to their limit before 8 December.

Problem: a plugin adds its own crossorigin attributes in the editor

Who is affected: a plugin that injects its own crossorigin attributes to make cross-origin media work in the editor. Cause: the media dev note says 7.2 stops rewriting crossorigin attributes on the editor page, and wp_print_media_templates() no longer adds crossorigin="anonymous" to audio and video tags. Fix: the note says plugins that added their own injection for this purpose can drop it, so ask the plugin author whether a 7.2 compatible version does.

The rollback rule

Before you update the live site on or after 8 December, take a fresh database backup with wp db export and a full copy of your site files using your host's backup tool or file manager. Keep both somewhere outside the site folder.

If the live update goes wrong, restoring that backup is your rollback. The wp core update command does have a --force flag that the docs describe as allowing an update "even when installed WP version is greater than the requested version", but the docs give no rollback procedure and say nothing about undoing database changes. So treat the pre-update backup as the only real way back. A backup taken after the update cannot help you here.

When to ask for help: if your site has custom code nobody on your team understands, or a checkout that earns real money every hour, ask your developer or host to run the copy test with you in week 1. It is far cheaper than fixing a broken shop on release night.

The one message worth forwarding

Copy this and send it to your developer, agency or whoever maintains your site:

"Hi, WordPress 7.2 is planned for 8 December 2026 and its release candidates are out now. Can we make a staging copy this week, update it to the newest 7.2 RC, and test login, forms, checkout in test mode, media uploads in Chrome and Firefox, our plugins and our custom code? Please check the PHP version in Site Health too, since PHP 8.2 security support ends 31 December 2026. Before any live update, let's take a full database and files backup so we can roll back. Can you send me a pass or fail list by 3 December?"

Test on a copy now, back up before the live update, and 8 December will be an ordinary Tuesday.

Reader questions

Does WordPress 7.2 switch my site to jQuery 4?

No. WordPress 7.2 ships jQuery Migrate 3.6.0 to prepare for jQuery 4, and the jQuery 4 update itself is tentatively planned for WordPress 7.3, depending on test results.

At what time will WordPress 7.2 be released on 8 December?

The proposed release party calendar on Make WordPress Core lists the final release for 8 December 2026 at 15:00 UTC. The post calls it a proposed calendar, so last-minute changes are possible.

Will WordPress 7.2 still run on PHP 7.4?

The requirements page says WordPress also works with PHP 7.4 and newer, but warns that those older versions have reached End Of Life and may expose your site to security vulnerabilities. The recommendation is PHP 8.3 or greater.

Is 7.2 the last big WordPress release this year?

Yes. The 7.2 schedule page says WordPress 7.2 is the final major release of 2026.

Where do I report a bug I find while testing 7.2?

The Make WordPress Test team asks for WordPress core bugs on Trac and editor bugs in the Gutenberg GitHub repository. Include your WordPress version, PHP version, database type and version, theme, active plugins, steps to reproduce, and any screenshots or logs.

Do I need a server to try WordPress 7.2 at all?

No. The RC1 announcement lists WordPress Playground at playground.wordpress.net/release, which runs in your browser with no setup. It is good for a quick look, but your own plugins and content still need a proper copy of your site.

Sources & further reading

  1. WordPress.org News: WordPress 7.1.5 Release
  2. Make WordPress Core: WordPress 7.2 release schedule
  3. WordPress.org News: WordPress 7.2 Release Candidate 1
  4. WordPress.org: Requirements
  5. WP-CLI: wp core update
  6. WP-CLI: wp db export
  7. PHP.net: Supported Versions
  8. Make WordPress Core: Preparing for jQuery 4 with WordPress 7.2
  9. Make WordPress Core: Media changes in WordPress 7.2
  10. WordPress Developer Resources: Debugging in WordPress

What changed

Rechecked the 8 December plan against the current WordPress 7.2 project page and RC1 announcement. Replaced brittle RC-number assumptions with a latest-official-build workflow, changed the plan to the actual 18-day window, hardened the WP-CLI database backup with a private unique verified path and off-server copy, and added original media.

Originally published . About our editorial updates.

Your next project deserves a better foundation.

Explore hosting built for your next chapter.

Explore hosting

Find your next answer.

Search published guides and articles.

Ctrl / ⌘ K to open · Esc to close