Web Design

WordPress 7.2 RC1: What Is in the Release, How to Test It, and What to Tell Clients Before December 8

A black-and-white studio photograph of a dressmaker's mannequin wearing a nearly finished jacket, the sleeves and hem still held with rows of straight pins and a tape measure draped over one shoulder, lit softly from the side against a plain gray backdrop, a visual for WordPress 7.2 RC1, the release candidate stage where the work is almost done and the last fitting checks happen before the final release

WordPress 7.2 RC1, the first Release Candidate for the last major WordPress release of 2026, is scheduled for November 17, 2026, and the final release for December 8. Release Candidate 1 is where WordPress freezes text strings for translators, creates the release branch and publishes the Field Guide of developer changes.

This post updates our WordPress 7.2 Beta 1 test plan. It covers the current schedule, what WordPress says is in 7.2, the changes that have surfaced since Beta 1, how to put the Release Candidate on a staging site, and what to tell clients before December 8. Dates and features are as WordPress published them through November 10, 2026. If RC1 slips, the order of steps here still holds; check the dates on the cycle page.

The short version: do one full test pass of your riskiest client sites on WordPress 7.2 RC1, then spot-check fixes on RC2 and RC3. New since our beta post: a /random/ URL that is on by default, admin menu icons rebuilt as SVG, a Secrets API for stored credentials, and translation updates you can pick one at a time. Tell clients the date now and agree on when their production update happens.

The WordPress 7.2 RC1 schedule

The WordPress 7.2 cycle page on Make WordPress Core lists these milestones. Release parties run in the #core Slack channel.

Milestone Date (2026) What the schedule says happens
Beta 5 November 10 Testing and bug fixes; Dev Notes written
Release Candidate 1 November 17 Field Guide published, hard string freeze, release branch created
Release Candidate 2 November 24 About page images updated; release post drafted
Release Candidate 3 December 1 Same as RC2
Dry run December 7 Release dry run, then a 24-hour code freeze
Final release December 8 WordPress 7.2 ships

The beta count changed after our Beta 1 post. That post listed four betas. The cycle page now lists five. Beta 3 shipped on October 28 inside the 7.1.4 security release, which we covered in our WordPress 7.1.4 post, and Beta 5 was set for November 10. The RC1 and final dates have not moved.

What WordPress says is in 7.2

The Beta 1 announcement on WordPress.org News is the fullest list WordPress has published so far. For editors and site owners, it highlights:

  • Responsive design controls for more blocks, including Gallery columns, cropping and aspect ratios per screen size.
  • Global Styles tools, including a filter that finds blocks with changed styles and styling for form elements.
  • Text shadows, set per block or as presets in theme.json.
  • Navigation editing from the editor sidebar.
  • Notes with emoji reactions, margin display and a minimized mode.
  • Client-side image processing that resizes, compresses and converts images in the browser before upload.
  • An “On This Day” dashboard widget that shows posts from the same date in past years.
  • Admin speed work, with assets loaded one by one for better caching and prefetching of likely next screens.

The post says these features may still be refined. The Field Guide at RC1 confirms what made it.

Developer changes to test on WordPress 7.2 RC1

The Beta 1 post lists these developer changes:

  • Secrets API. WordPress calls it “a standardized, secure way to store sensitive credentials,” with encryption at rest, credential rotation and custom storage providers.
  • Random content redirects. A URL that sends visitors to a random post. More on this below.
  • Abilities API additions for accessing and querying data. Our Abilities API explainer covers the basics.
  • Interactivity API additions for rendering trusted HTML and reactive navigation.
  • HTML API and block supports improvements.

The Secrets API matters to agencies that store API keys for AMS, CRM and AI integrations. It bears on the credential storage problem we described in our Connectors API encryption status check. Read its Dev Note in the Field Guide before you move any plugin’s keys into it.

Two items from our beta post still apply. The NO_BACKSLASH_ESCAPES SQL mode is turned off for WordPress’s own database session, per the October 9 Dev Note. And the wp_kses() rebuild was targeted at 7.2 or 7.3. Check the Field Guide to see whether it landed.

The /random/ URL is on by default

Aaron Jorbin’s November 5 Dev Note describes a new /random/ endpoint that sends a visitor to a randomly chosen published post. It is on by default.

Variants include /random/category/<slug>/, /random/tag/<slug>/, /random/author/<name>/ and one per eligible custom post type. Among built-in types, only posts qualify. The base can be renamed on the Permalinks screen.

To turn it off, the Dev Note gives one line:

add_filter( 'wp_enable_random_content_redirect', '__return_false' );

A custom post type can opt out with 'randomable' => false when it is registered.

The Dev Note itself says nothing about caching or load. In the comments, readers point out that the query orders by RAND(), which gets slower as the posts table grows, and one commenter reports a case where a page cache could serve the same random post to everyone. A maintainer called that a bug worth fixing. Test it on staging with your page cache and CDN on.

Decide on /random/ before December 8. Large archives, membership sites and sites behind a page cache should test the endpoint on WordPress 7.2 RC1. If a client has no use for it, add the filter in a small plugin before the production update.

Admin menu icons are now SVG

Ashar Fuadi’s November 5 Dev Note says the admin bar and sidebar menu icons are now inline SVGs from @wordpress/icons, replacing Dashicons font glyphs drawn with CSS ::before.

Most plugins need no changes. Core keeps its dashicons-* values, and other Dashicons, image URLs and base64 SVGs render as before. What can break is custom CSS:

  • Admin color schemes that style the ::before element also need to style .ab-icon or .wp-menu-image, because the SVG takes its color from its parent.
  • A content rule on .ab-item::before no longer replaces an admin bar icon by itself.
  • CSS that targeted a Dashicon class should target the menu item’s id or menu-icon-* class instead.

For new work, add_menu_page() and register_post_type() accept a registered icon name such as core-admin/pin. The note says to use the core-admin collection for admin icons, not core.

Ipsum, the new default theme

Ipsum is a minimal blog theme "planned to be bundled in WordPress 7.2," according to the introduction post. It is the first default theme named for something other than a year.

The Beta 4 announcement says it is still being refined. Recent changes include clearer keyboard focus indicators, more descriptive screen reader links, better right-to-left language support and better touch target spacing.

If you test plugins against the default theme, switch your baseline at WordPress 7.2 RC1.

Translation updates you can choose

The Beta 4 post also notes a change site owners will see: "Administrators can now review and selectively install translation updates." The Updates screen lists each translation update on its own.

On multilingual association and university sites, someone can now hold back a translation update that changes approved wording.

How to put WordPress 7.2 RC1 on a staging site

The 7.2 beta posts are clear about production: "Please do not install, run, or test this version of WordPress on production or mission-critical websites." Use a staging copy with a recent database. WordPress documents four ways in:

Method How Best for
WordPress Beta Tester plugin “Bleeding edge” channel, “Beta/RC Only” stream Staging sites managed in the admin
WP-CLI wp core update --version= plus the release string Scripted updates across many staging sites
Direct download Zip from the announcement post Hosts without WP-CLI
WordPress Playground Browser instance linked from the announcement Quick looks with no setup

The Beta Tester plugin page says "Don’t forget to backup before you start!" It also has settings to skip some emails, which helps keep staging from mailing real users.

For WP-CLI, the Beta 4 post used wp core update --version=7.2-beta4. Use the exact version string the RC1 announcement gives. Then run wp core version to confirm what is installed.

To go back, restore the staging snapshot. The WP-CLI documentation says --force will "Update even when installed WP version is greater than the requested version," but a database upgrade may already have run. A snapshot is the cleaner rollback.

A test pass for WordPress 7.2 RC1

Run the checklist from our beta post on the riskiest sites first. Then add these:

  1. Load /random/ with the page cache and CDN on. Check speed and whether every visitor gets the same post.
  2. Open the admin with each custom color scheme and admin CSS your team ships. Look for blank or wrong-colored menu icons.
  3. Upload large images in the editor and confirm the output size and format you expect.
  4. Run translation updates one by one on a multilingual site.
  5. Read the Field Guide and list every Dev Note that touches your plugins.

Report Core bugs on Trac. On RC2 and RC3, retest only what failed.

What to tell clients before December 8

Clients need four things from you:

  • The date. WordPress 7.2 is scheduled for December 8. Your team is testing their site on a copy first.
  • When their site updates. Agree on a date after the release and after your own checks, and say whether it lands before or after any holiday freeze.
  • What they will see. Admin menu icons look different. Editors get Notes reactions, an On This Day widget and new design controls.
  • What they need to decide. Whether to keep the /random/ URL, and who approves translation updates.

If a client site is not yet on 7.1.4, or on the latest release of its older branch, fix that first. A major update should not be the first update a site has had in months.

Frequently Asked Questions

When is WordPress 7.2 RC1?

The WordPress 7.2 cycle page schedules Release Candidate 1 for November 17, 2026. RC2 is set for November 24, RC3 for December 1 and the final release for December 8.

What changes at Release Candidate 1?

The schedule lists a hard string freeze, a new release branch and the Field Guide, which collects the Dev Notes from the beta cycle. After RC1 the focus is on bug fixes.

Can we install WordPress 7.2 RC1 on a live site?

No. WordPress asks testers not to run pre-release versions on production or mission-critical sites. Use a staging copy and update production after the final release.

What is the /random/ URL in WordPress 7.2?

It is a new endpoint that redirects visitors to a random published post, with variants by category, tag, author and custom post type. It is on by default. A one-line filter, wp_enable_random_content_redirect, turns it off.

Will the new admin icons break our plugins?

Most plugins need no change, according to the Dev Note. Custom CSS that styles or replaces Dashicons through ::before is the main risk. Test admin color schemes and any admin CSS on staging.

What is the Secrets API?

WordPress describes it as a standard, secure way to store sensitive credentials, with encryption at rest, rotation and custom storage providers. Read its Dev Note in the Field Guide before moving plugin keys into it.

What is Ipsum?

Ipsum is the minimal blog theme planned as the 7.2 default. WordPress was still refining its accessibility, right-to-left support and patterns during the betas.

How do we install WordPress 7.2 RC1 with WP-CLI?

Run wp core update with the –version flag and the exact version string from the RC1 announcement. The Beta 4 post used 7.2-beta4 in the same place. Confirm with wp core version afterward.

What if WordPress 7.2 RC1 is delayed?

Follow the same steps on whatever date it ships. Check the Make WordPress Core cycle page for the current schedule, since the final release date moves only if WordPress changes it there.

Digital Matters

Web Design Desk