How to Test WordPress 7.2 on a Staging Site Before Release

WordPress 7.2 Beta 1 arrived on October 20, 2026, and the final release is scheduled for December 8. For a US small business, that date lands just after Black Friday and Cyber Monday, which is exactly when you do not want surprises on your live site.

The good news is that you do not have to wait for the final release to find out how your theme and plugins behave. You can test the beta on a copy of your site now, while there is still time for plugin developers, and WordPress itself, to fix problems. This guide shows how to set up that test and what to check.

What the 7.2 Beta Adds

The WordPress 7.2 Beta 1 announcement lists several changes. Responsive styling controls reach more blocks, Global Styles gets a "Customized" filter, text shadows arrive as a block setting, and navigation items can be managed from the Site Editor sidebar. The editor adds emoji reactions in Notes, and images can be resized, compressed and converted in the browser before upload. Admin icons are also being replaced.

Several of these touch things a small business site uses every day: media uploads, menus, and the admin screens your team works in. That is why testing on your own setup matters more than reading the feature list. A beta is also a moving target, so details can change between builds.

The 7.2 Release Timeline

The WordPress 7.2 release schedule lays out one build a week until the final release. Dates can shift, so check the schedule page before you plan around them.

Thanksgiving falls on November 26 and Black Friday on November 27, so two release candidates and the final release straddle the busiest shopping days. Z.com's Black Friday website readiness guide suggests freezing major changes about a week before Thanksgiving. Testing the beta on a copy fits that plan, because it adds no risk to your live store.

Choose Where to Test

WordPress's call for testing and the beta announcement describe several ways to run the beta. Pick the one that matches how closely you need to mimic your real site.

How to Test the Beta Step by Step

These steps assume a staging copy or a local site. The WordPress announcement says plainly not to install, run or test the beta on production or mission-critical websites.

• Back up first. Save your files and database before you start, even though you are working on a copy.
• Create the copy. Clone your live site to staging or a local environment, then confirm you are looking at the copy and not the live site.
• Make the copy safe. Put staging behind a login, such as HTTP authentication or an IP allowlist from your host, and turn on "Discourage search engines" under Settings > Reading. Search exclusion only asks crawlers to stay away, so it is not access control. Keep only the customer and order data you need, or anonymize it. Put payment gateways in test mode, pause plugins that send customer emails, and disable outbound webhooks and production integrations or point them at test endpoints, so testing never contacts real customers or charges real cards. Our guide to adding Stripe or PayPal checkout to WordPress covers test payments.
• Update everything else first. Bring WordPress, your theme and your plugins up to date on the copy, using the current stable release. Turn on logging (next step), run the checks in "What to Test on a Small Business Site" below, and note any errors that already exist. Save a backup or snapshot of this baseline that you can restore.
• Turn on debugging. On staging only, edit wp-config.php and change any existing definitions rather than adding duplicates. Set WP_DEBUG to true, set WP_DEBUG_LOG to true to save errors to wp-content/debug.log, and set WP_DEBUG_DISPLAY to false so errors are logged but not shown on screen. Keep the log private and redact sensitive details before you share it. The WordPress debugging guide explains each setting.
• Switch to the beta. Change only WordPress core. Install the WordPress Beta Tester plugin, open Tools > Beta Testing, choose the "Bleeding edge" channel and the "Beta/RC Only" stream, then run the update from the Dashboard. Repeat your checks and compare them with the baseline, and review the error log for new notices, warnings and fatal errors.

Prefer the command line? The announcement lists wp core update --version=7.2-beta1 as an option, and a direct zip download is available too.

What to Test on a Small Business Site

You do not need to test every feature. Focus on the paths your customers and your team use every week:

• Your homepage, top landing pages and menus load and look right on desktop and mobile.
• You can log in to wp-admin, edit a real page, and save it with your usual blocks and patterns.
• Media uploads work. The beta adds in-browser image processing, and the call for testing says to try it in a Chromium-based browser and confirm Safari and Firefox fall back to server-side processing without failing.
• Contact forms, signup forms and booking tools submit and send their notifications.
• Cart and checkout complete a test order from start to finish, if you sell online.
• Your SEO, caching and security plugins still run without warnings.
• Tools > Site Health shows no new critical issues, and permalinks still resolve.
• The browser console and the PHP error log show nothing new.

What to Do If Something Breaks

First, isolate the cause. Deactivate plugins one at a time on the copy, or switch to a default theme, and see when the problem disappears. Then tell the plugin or theme developer, and report the issue to WordPress if it looks like a core bug.

The call for testing asks reporters to include the WordPress version (for example 7.2-beta1), PHP version, database type and version, theme, active plugins, reproduction steps, and any screenshots or logs. Core bugs go to WordPress Trac, editor bugs go to the Gutenberg issue tracker, and general beta questions can go to the Alpha/Beta support forum.

Common Mistakes to Avoid

Deciding When to Update Your Live Site

Testing the beta gives you information, not a deadline. When the final release arrives, check that your theme and key plugins list support for it, take a fresh backup, and update during a quiet period. Until then, keep applying security updates for the WordPress version you run now.

Frequently Asked Questions

Sources and Further Reading

• WordPress.org News: WordPress 7.2 Beta 1
• Make WordPress Test: Help Test WordPress 7.2
• Make WordPress Core: WordPress 7.2 Release Schedule
• WordPress Beta Tester Plugin
• WordPress Developer Resources: Debugging in WordPress