WordPress 7.2 RC1 Is Available for Testing Ahead of December Release

WordPress has released the first 7.2 release candidate for testing ahead of the final release on December 8, 2026. It should be tested on staging sites, not production sites.

· 4 min read · 4 comments

WordPress released the first 7.2 release candidate for testing on November 17, 2026, according to WordPress News. RC1 is still in development: WordPress recommends testing it on a staging site or server rather than installing it on production or other critical sites. The final release of WordPress 7.2 is scheduled for December 8, 2026.

What’s Changed in RC1

The release candidate includes bug fixes, accessibility improvements, and compatibility updates. Since Beta 5, developers have refined client-side media uploads and the redirect-to-random-post feature. They have also improved keyboard navigation in the admin dashboard: a skip link lets users bypass part of the interface.

Less visible changes are worth considering when checking site compatibility. Plugin dependency messages and script module translations have been updated. Developers have also worked to make the HTML API and Interactivity API more reliable, continued refining the Abilities API, and updated the PHPMailer, Requests, getID3, and sodium_compat libraries. These names matter most to people checking how themes, plugins, and other components work with the new version of WordPress.

In the block editor, fixes address duplicated content, keyboard use on iOS, and revision previews. A separate Interactivity API improvement prevents a late navigation response from replacing newer content. Other fixes cover plugin installation workflows, featured image compatibility, and link suggestions. The admin interface is also continuing its move to SVG icons.

RC1 also offers a chance to assess WordPress 7.2 changes announced earlier. These include the new default Ipsum theme, expanded responsive design and gallery settings, and global styles and typography tools. WordPress has also announced improvements to Canvas Notes for collaboration and a new DataForm-based block settings inspector. For more on the start of this development cycle, see our article on WordPress 7.2 Beta 1.

Other changes include faster media uploads and image processing, admin navigation, and resource loading. The list of features also includes an “On This Day” widget, random post discovery, and improved management of translation updates. WordPress reports improvements to accessibility, security, and PHP 8.6 compatibility. All of this can be tested before release, but RC1 itself is not yet intended for production sites.

What to Check Before the Final Release

For site owners, the main question right now is not when to update a production site, but where to test the upcoming version safely. WordPress warns that development is ongoing. On a staging site, you can run through familiar tasks: open pages, edit blocks, upload images, and navigate the admin dashboard. It is also worth testing the update process itself, which developers describe as an important part of preparing for release.

If your site relies on a theme or plugins, their compatibility with 7.2 needs attention. Plugin authors are advised to finish testing against RC1 and update the “Tested up to” value to 7.2 in their plugin’s readme file. WordPress asks that compatibility issues be reported in detail on the support forum. Hosting providers are encouraged to test the release on their platforms to check compatibility and how updates go on customer sites.

Marketers and editors should focus on everyday tasks: working with blocks, photos, galleries, links, and revision previews. Developers should check plugin dependencies and workflows that use the APIs that have changed. That way, testing goes beyond reviewing a list of new features: it shows whether the actions your site depends on still work after the update. WordPress encourages testing both the upgrade process and the new version’s features.

My Take: Start with Familiar Tasks

I wouldn’t judge RC1 by the length of its feature list. For an apartment catalogue, I’d be more interested in whether the person managing the site can replace photos, correct a description, and keep property details up to date without unnecessary obstacles. On a staging site, I’d go through that familiar editorial workflow first, then explore the new design settings.

I think it makes sense to use RC1 for preparation and wait for the final release before updating a production site. If the current CMS is stable and easy to maintain, there’s no reason to change your approach for the sake of a new feature. But agreeing in advance on who will test the site and who will be responsible for photos, accessibility, and rental terms after the update is useful regardless of the release date.

Sources

Where the news comes from. The text is a retelling in the author’s own words; the facts come from the source, the opinion is the author’s.

  1. WordPress 7.2 Release Candidate 1 wordpress.org

About the author

Elena Georgiou

owner of a property rental company

I rent out apartments in Cyprus and am updating a website with a property catalog. I recommend deciding in advance who will update photos, availability, and rental terms.

All posts by the author

Leave a comment

Not published. We’ll send a link to confirm your comment.

No links or ads. Your first comment is published after review. By sending a comment you agree to the privacy notice.

  1. A skip link and smoother media uploads—nice. I’ll give RC1 a spin on staging; my production store already has enough excitement from plugins that promise to do absolutely everything.

    1. Just to clarify, the skip link is in the admin dashboard, so it’s worth checking keyboard navigation there too—not only the front end 🙂

      1. @yervand.s I’d also check the skip link with the keyboard at different admin screen sizes; a link can be present but still awkward to reach or use when the dashboard layout changes.