WordPress 7.2 Beta 1 Is Due 20 October: A Staging Test Plan

WordPress 7.2 reaches Beta 1 on 20 October 2026, and the final release is scheduled for 8 December. Beta 1 is also the point where new features stop being committed, so what a site owner finds in the following weeks is close to what will ship. The official 7.2 page lists the dates, and the main point of the schedule is that the bugs found between now and mid-November are the ones that get fixed.

The schedule

The dates on the Make WordPress Core page are:

• Beta 1: 20 October 2026, Beta 2: 27 October, Beta 3: 3 November, Beta 4: 10 November.
• Release Candidate 1: 17 November, RC2: 24 November, RC3: 1 December.
• Dry run and 24-hour code freeze: 7 December.
• Release: 8 December 2026.

The page says patches for enhancements will not be committed after the posted dates, and that after feature freeze only bugs are addressed, with regressions as the highest priority. Some third-party articles give wider release windows. The Core page is the authority, and the roadmap itself says that everything on it is being pursued without being guaranteed.

How to test without risking a live site

Use a copy of the production site on a staging host, with its database cloned, not the live site. The WordPress Beta Tester plugin lets a site upgrade to a nightly, beta or release candidate build through the normal updater, and its page advises taking a backup first. Its default setting follows the point release channel, so the bleeding-edge option has to be chosen deliberately.

Before upgrading, write down three journeys that earn money or leads, for example a checkout, a contact form and a search, along with the PHP version, the theme and the active plugin list. Run each journey after every beta build. A failure that appears after Beta 2 and was absent in Beta 1 points at a specific change, which is far more useful in a bug report than a general statement that something broke.

What to look at first

Four items from the October developer roundup and the 7.2 developer notes are concrete enough to test directly:

1. HTML sanitising. The wp_kses() rebuild may land in 7.2 or 7.3. Content from comment forms and form plugins is the place to compare output, as set out in the post on testing the wp_kses() rewrite.
2. Database mode. 7.2 turns off the NO_BACKSLASH_ESCAPES SQL mode for WordPress’s own connection. A site that relied on it needs a db.php drop-in.
3. Block and theme styles. Gutenberg 24.1 added block supports to nearly every core block, and Accordion, Tabs, Tab Panel and Post Template now output has-link-color and related classes. The roundup advises checking for specificity collisions with theme link styles. Gallery CSS is also now scoped to :where(.is-layout-flex), so Grid galleries should be checked against theme CSS.
4. Icons. About 330 core icons are now stroke-based and set fill: none inline, so fill props and CSS fill rules no longer recolour them, and custom code should use CSS color instead.

The new default theme

The developer roundup says the new default theme, Ipsum, ships with 7.2 and replaces year-based naming. It is a minimal blog theme with style variations that recolour the whole page, and the team states that every combination meets WCAG AA. A site running a child theme of the previous default should open the front end and the editor under Ipsum on staging, not assume that the parent behaves the same way.

What to report, and where

A regression found in Beta 1 is more valuable than one found in RC3, because the schedule treats regressions as the first priority after feature freeze. Report through Trac or the relevant GitHub repository with the version, the PHP version and the plugin list. The previous major release is covered in the post on WordPress 7.1 and its effect on speed and search, and what broke when the editor moved into an iframe is covered in the post on the iframed post editor.

If staging cannot be arranged before 20 October, Beta 4 on 10 November is the last practical date to run the same checks before the release candidates, and a site that skips both finds its regressions on 8 December on the live site.