On December 8, 2026, WordPress 7.2 is due to be released, the last major version of the year. The first Release Candidate, a nearly finished test version, is scheduled for today; two more will follow on November 24 and December 1. From now on, the developers will only fix bugs in the new version that are found during testing.
By default, WordPress does not install a new major version on its own, unlike the small maintenance and security updates. So you decide when 7.2 arrives on your website, and you have a good three weeks of lead time. A change on the server also falls into the same weeks: PHP 8.6 is due to be released on November 19, and PHP 8.2 will only receive security updates until the end of December.
This guide is about the preparation: what you check beforehand in the backend, what a backup looks like that lets you restore the old state, where you can test the new version safely, and how you install it in the end.
When is WordPress 7.2 coming, and does it come on its own?
The planned date is December 8, 2026, as stated in the Core team's schedule and in the announcement of the fifth beta. A Release Candidate is a test version that is considered finished as long as no major bugs turn up. Testing with these versions is worthwhile, because no new features will be added.
Der Weg zu WordPress 7.2
Geplante Termine laut Zeitplan des WordPress-Core-Teams
17. November 2026Erster Release Candidate
24. November 2026Zweiter Release Candidate
1. Dezember 2026Dritter Release Candidate
8. Dezember 2026WordPress 7.2 erscheint
Geplante Termine, sie können sich verschieben
Quellen: Make WordPress Core, WordPress News
Since version 3.7, WordPress has installed only maintenance and security updates in the background, such as the step from 7.1.3 to 7.1.4. For a new major version, according to the guide to updating, you click "Update now" yourself.
This does not apply if automatic updates for all versions are enabled on your website: via the setting under Dashboard, Updates, or via the constant WP_AUTO_UPDATE_CORE in the wp-config.php. With the value true, according to the documentation on automatic updates, WordPress also installs major versions on its own. So first check which update setting applies on your website. If automatic updates are active for all versions, switch back to maintenance and security updates for the test phase. Otherwise 7.2 will land untested on the live site on December 8.
What do you check beforehand in Site Health?
The PHP version and all open notices. You'll find both under Tools, Site Health. According to the WordPress documentation, the Status tab sorts the findings into critical issues, recommended improvements, and passed tests. The Info tab lists the versions of WordPress, PHP, database, themes, and plugins, and with the "Copy site info to clipboard" button you copy everything at once.
The Status tab separates critical issues from recommended improvements; here WordPress reports a publicly accessible error log (screenshot: WordPress 7.1.4, test installation, 17.11.2026).
Copy this report before the update and save it with the date. Later it shows you which plugin version was installed beforehand and helps with comparison against the test copy.
In its requirements, WordPress recommends PHP 8.3 or newer, plus MariaDB from 10.11 or MySQL from 8.4. According to the PHP project, PHP 8.2 only receives security updates until December 31, 2026. If your website still runs on it, the switch is due anyway.
According to the announcement of the fifth beta, WordPress 7.2 is meant to fully support PHP 8.6; all known issues in WordPress core have been fixed. Whether your plugins and your theme keep up, you have to check yourself.
Don't switch PHP and WordPress on the same day, otherwise in case of an error you won't know which change triggered it.
What does a backup look like that lets you restore the old state?
It always consists of two parts: the database and the files. According to the WordPress documentation on backups, posts, pages, and settings are in the database, while themes, plugins, uploads, and the wp-config.php are in the file folder. If you only copy the files, you don't have a complete backup, because the database is located outside the WordPress folder.
Backup Order
This is what the WordPress documentation recommends for a complete backup set
Backing up
Export the database first
Then copy all files
Store both at the same time and in the same folder
Restoring
Restore the files first
Then import the database
If you have new credentials, adjust the wp-config.php
Source: WordPress documentation
The docs recommend a fixed order: when backing up, the database first, then the files; when restoring, the reverse. With command-line access, you export the database to an SQL file using wp db export, as described in the WP-CLI docs. Without a command line, your hosting provider's backup tool or a backup plugin will help. Keep three to five recent backups in different locations, such as on the server, in cloud storage, and on your computer. According to the docs, you should occasionally supplement automatic backups with a manual backup to see whether they work.
How to schedule backups in everyday use and where they should be stored is covered in our guide Securing WordPress. How to create a backup with a plugin and restore it is shown in the lesson on backup and restoration in the beginner course.
Restore your backup into a test copy once before you rely on it. That also gives you the copy for the next step.
Where do you test 7.2 without endangering the live site?
On a copy of your website. In its call for testing 7.2, the WordPress testing team explicitly advises against trying out beta and test versions on the live site, because your visitors would see every error. There are four ways to create the copy, which differ in effort and informative value.
Testing is done on a copy with your own plugins and content, never on the live site.
Method
What you need
What you test with it
WordPress Playground
just the browser, no installation
new features on a fresh installation, without your content
Local test environment
a development environment on your computer, such as wp-env
your website from the backup, with your plugins and content
Staging at your host
your hosting provider's staging feature
the most realistic copy: same server, same PHP version
WP-CLI
access to the command line
installing a specific test version, for example with wp core update --version=7.2-RC1
On a local copy or in the staging environment, the easiest way to install the test version is with the WordPress Beta Tester plugin. According to the announcement for the fifth beta, you select the "Bleeding edge" channel there and then "Beta/RC Only". The test version then appears under Dashboard, Updates.
Only a test on a copy with your own plugins, your theme, and your content is meaningful. Playground is suitable for a first look at the new features, but does not replace this test.
What belongs on your test list?
Everything your website needs to be able to do day to day, and the areas that 7.2 changes. The list below is based on the general checklist from the call for testing.
Your test list for WordPress 7.2
Check off on the test copy before the live site gets the update
Error log enabled, display for visitors off
Theme and plugins updated on the copy
No plugin deactivated after the update
No new warnings in Site Health
Templates, pages, and forms checked
Media uploaded, edited, galleries viewed
Custom theme modifications still there
Sources: Make WordPress Test, WordPress Developer Resources
Enable the error log: In the wp-config.php, you set WP_DEBUG and WP_DEBUG_LOG to true and WP_DEBUG_DISPLAY to false. WordPress then writes errors to the debug.log file in the wp-content folder instead of displaying them on the page (debug docs). Because this file may be publicly accessible, Site Health classifies it as a critical issue. Therefore, turn the log off again after the test.
Update theme and plugins and then check in the plugin list whether WordPress has deactivated a plugin on its own.
Open Site Health again and compare it with the earlier report. Note any new warnings along with the plugin name and version.
Click through templates and pages: home page, post, archive, and your most visited pages.
Submit forms and check whether the message arrives where it belongs.
Test media: upload an image, crop it, and view a gallery.
Check theme customizations: Are your changes in the Site Editor or in the Customizer still there after the update?
If you run a shop, a booking system, or a members area, you play through exactly these processes once from start to finish, from the shopping cart to the confirmation email. The call for testing explicitly recommends checking the processes for which you use your website.
In addition, there are three changes in 7.2 that may be noticeable in the backend. WordPress loads the backend scripts individually instead of bundled. This may affect older plugins with their own backend pages. Plugins that ship their own copies of certain WordPress packages should, according to the developer note, get an update before the release. Otherwise their styling rules (CSS) may mix with those of the backend (our news on this).
In addition, according to the announcement for the fifth beta, WordPress sends an email as soon as someone creates an application password, that is, a separate password for an app or interface.
How do you install the update, and how do you get back?
With a current backup made right beforehand and at a time when things are quiet. Once the test has gone smoothly, you open Dashboard, Updates and start the update with one click.
The backup right before the update is your way back: first restore the files, then the database.
Leave the browser tab open until WordPress is finished. According to the update guide, WordPress briefly switches to maintenance mode in the meantime, and visitors see a notice. If the website is still stuck in maintenance mode afterwards, there is usually a file named .maintenance in the main folder. Once you are sure that no update is still running, you delete it via FTP or through your hosting's file manager.
According to the documentation, there is no fixed order for WordPress and plugins. Some plugins want to be updated before the core, others already need the new version.
Your test copy has shown you which order works for you. After that, you install the remaining updates for plugins and themes and click through the website once.
If something goes wrong, you restore the backup from earlier: first the files, then the database. If the one-click update does not work at all, the documentation describes a manual way in which you replace the wp-admin and wp-includes folders and leave the wp-content folder untouched.
What this means for you
Three weeks are enough for a thorough test if you start now. The release candidates give you fixed dates for this.
Your roadmap to December 8
Following the dates from the schedule for WordPress 7.2
This weekCheck update setting and Site Health, save the report
By November 24Create a backup, build a test copy, test the first release candidate
From December 1Test the third release candidate, compare plugin updates
From December 8Current backup, install update, click through the website
Sources: Make WordPress Core, Make WordPress Test
Today: Check under Dashboard, Updates whether major versions are installed automatically, and copy the report from Site Health.
By November 24: Create a full backup, restore it into a test copy, and work through the test list there with the first release candidate.
From December 1: Repeat the test with the third release candidate and check whether plugins that showed errors in the first test have received updates in the meantime.
For client websites: Plan a separate time window for each website and tell your clients beforehand when you will install the update and that the website will be briefly in maintenance mode.
How to keep themes and plugins up to date in everyday use is explained in a separate lesson of the course WordPress for Beginners.
Our assessment: You do not have to install WordPress 7.2 on the release day. Because a major version does not arrive on its own, you can wait a few days until your most important plugins have caught up. You should not postpone the update indefinitely, though, because the WordPress documentation advises always using the current version. With the test on a copy, clicking "Update now" becomes routine instead of a risk.
Status of the information: November 17, 2026. The dates come from the WordPress Core team's schedule and may change.