WordPress published its first 7.2 release candidate on 17 November 2026 and announced a planned final release on 8 December. For a site owner, the candidate is a chance to see whether the next version works with the theme, page builder and plugins the business relies on.

A release candidate is a pre-release build made available for testing. WordPress describes RC1 as including further fixes and accessibility and compatibility improvements. Use a staging copy with the same setup as the production site so a successful test is relevant to the actual upgrade.

Back to the 22 November Weekly Highlights

Choose the test environment

Ask your host for a staging copy and confirm the restore point. Disable delivery to real customers and route forms and order emails to controlled test inboxes.

Record what works before changing versions

Capture the core, theme, PHP and plugin versions on the staging copy. Run a mobile enquiry and a desktop editing check first. Photograph or screenshot a representative page and note what happens at submission. Fix or document any pre-existing issue so it doesn’t get mistaken for a release regression.

Test the page builder and the visitor journey

For a WPBakery site, open a representative page in the builder and confirm that rows and modules load. Edit a small piece of copy, save it and view the result on mobile and desktop. Check a grid or query that pulls posts by tag. Then submit an enquiry and verify both the visitor confirmation and arrival in the test inbox or CRM.

Add store and editorial checks where they apply

In a store’s test mode, try a product variation, add it to the basket and step through checkout using a sandbox payment setup. Review shipping and order emails. For a site that publishes regularly, check draft previews, scheduled publishing and one post with a featured image. If your team uses the block editor, test reusable patterns and review steps with the roles people actually have.

Make the production decision from the results

List failed checks with a URL, steps to repeat, expected behaviour and a screenshot. Assign a person to check whether a theme or plugin update fixes each failure. Before moving the stable release to production, repeat the important checks against that release and confirm that a usable restore point is available.

Baseline

Record a passing test on the current version.

Stage

Install the candidate on the isolated copy and repeat the same checks.

Approve

Repeat critical tests on the stable release before the live upgrade.

Questions readers may have

Can I use RC1 on my public site?

Use a staging or test copy. WordPress publishes candidates so people can identify issues before the final release.

Will block editor improvements change my WPBakery pages?

Test the editing and public display of a representative WPBakery page. Core, theme and plugin compatibility determines how your particular site behaves.

Sources and further reading