WordPress 7.2 Beta 5 is out, and RC1 arrives in just a few short days on November 17, 2026. You can also expect the 7.2 Field Guide and Source of Truth at the same time.
The final release is scheduled for December 8. So this will be the last monthly roundup before WordPress 7.2 ships, so if you haven’t started testing your plugins and themes against the betas, well…it’s a good time to start.
WordPress 7.1.4 shipped on October 28 with 13 security fixes, several of them in the Interactivity API. A week earlier, the PHP project released fixes for two critical vulnerabilities. Do yourself or your clients a favor and make sure that you’re updated across the board.
You can test the latest with the WordPress Beta Tester plugin, wp core update --version=7.2-beta5, or a Playground instance. The Help Test WordPress 7.2 post walks through each feature.
Like I did last month, I’m experimenting with the monthly roundup format. I’m sticking the highlights that I think are most important at the top and including everything else in the Want more? section at the end of the post.
Table of Contents
The Secrets API lands in 7.2
Until now, every plugin that needed an API key stored it in the options table as plain text. WordPress 7.2 adds a Secrets API that encrypts credentials at rest, keeps a previous version for rotation, and lets hosts swap in their own storage through a secrets.php drop-in.
New functions include:
wp_set_secret()wp_get_secret()wp_delete_secret()wp_retire_secret_version()
The convention for secret names is plugin-slug/secret-name. It’s also worth noting that wp_get_secret() returns either a WP_Secret object, null, or WP_Error. And the secret is masked until you ask for it via reveal() on the secret object.
Here’s some example code showing how to use it:
function pluginslug_get_api_key()
{
$secret = wp_get_secret('plugin-slug/api-key');
if ( is_wp_error( $secret ) ) {
// The secret exists but can't be read. Tell the user.
return '';
}
return $secret ? $secret->reveal() : '';
}
Secrets are encrypted with a key from a new WP_SECRETS_KEY constant in wp-config.php. New installs get this automatically, and Site Health tells existing sites how to add it.
There’s no admin UI for secrets in 7.2; that’s planned for a later release.
Admin bar and menu icons are now SVG

The icons in the admin bar and sidebar menu are now inline SVGs from the core-admin icon collection instead of Dashicons font glyphs. If your plugin uses dashicons for menus, they won’t disappear. The equivalent core-admin icon will be swapped in.
However, any CSS rule that uses ::before to color, hide, or replace icons will no longer work or could break the design. This is because the icon is now a real <svg> element. To see how to update these cases, read the Developer Note: SVG icons in the admin bar and menu in WordPress 7.2.
add_menu_page(), register_post_type(), and WP_Admin_Bar::add_node() all now accept the new SVG icons. Here’s an example of using it with a fallback check for pre-7.2:
add_menu_page(
__('Notes', 'pluginslug'),
__('Notes', 'pluginslug'),
'manage_options',
'pluginslug-notes',
'pluginslug_render_notes',
function_exists('wp_is_valid_icon_name') ? 'core-admin/pin' : 'dashicons-admin-post'
);
You can also register your own collection and use those icons with wp_register_icon_collection().
Random content URLs
WordPress 7.2 is adding a new /random URL that sends visitors to a random published post. And it works with archives, such as /random/category/news and /random/author/username. For a full overview, read Your Content Is Going To Get More Random!
register_post_type() also has a randomable argument to control whether the post type is included. It defaults to true for publicly queryable post types with an archive. To opt a post type out, use:
register_post_type('plugin_event', [
'public' => true,
'has_archive' => true,
'randomable' => false,
]);
The random pick runs through the main query, so your existing pre_get_posts callbacks apply. To change only random requests, check for them with wp_is_random_content_query(), like so:
add_action('pre_get_posts', static function (WP_Query $query) {
if (wp_is_random_content_query($query)) {
$query->set('category__not_in', [42]);
}
});
You can also disable the feature altogether by filtering wp_enable_random_content_direct and returning false.
Admin scripts and styles are no longer concatenated
The October roundup mentioned that the 7.2 roadmap planned to replace script and style concatenation with prefetching. That’s now done. Admin and login screen assets load individually, and WordPress prefetches what the next screen is likely to need. load-scripts.php and load-styles.php are deprecated and no longer requested.
If your plugin links to either file directly, hooks into the concatenation process, or assumes certain scripts print in the <head>, test it against Beta 5. Some scripts that used to be bundled in the head now print in the footer.
React 19 is on by default in Gutenberg
Gutenberg 24.2 turned on React 19 by default for sites running the plugin. Sites with a theme or plugin known to be incompatible stay on React 18, and you can switch it off under Gutenberg > Experiments in your WordPress admin.
This is a Gutenberg plugin change, not a WordPress 7.2 one. Even still, now is a time to be testing to ensure compatibility across all your plugins, themes, and sites.
Interactivity API: data-wp-html and navigation state
Two Interactivity API additions from Gutenberg 24.2 are part of 7.2. The first is the data-wp-html directive, which renders HTML from the store just like data-wp-text does for text:
<div data-wp-interactive="pluginslug">
<div data-wp-html="state.summary"></div>
</div>
It will only accept values that you’ve explicitly marked as trusted via asDangerousHTML() like so:
import { asDangerousHTML, store } from '@wordpress/interactivity';
store('pluginslug', {
state: {
get summary() {
return asDangerousHTML('<p>Doors open at <strong>7pm</strong>.</p>');
}
}
});
The second feature is a reactive navigation lifecycle for the router. state.navigating lets you know when a client-side navigation is in progress, and state.initiator tells you which block started it.
Core entity actions and fields move to the server
Gutenberg 24.3 registers Core’s entity actions and fields on the server and moves them into the @wordpress/core-actions and @wordpress/core-fields script modules. During this process, “fields” were renamed to “entity fields,” and the DataForm-based post inspector was stabilized.
If you’ve been following the DataViews and DataForms work, this is the groundwork for registering your own fields and actions the same way. If you extend the post sidebar, test your panels against the DataForm inspector now.
Style text input states in theme.json
Themes could already style text inputs through the textInput element. In 7.2, you can also style these inputs based on their state. The following states are now allowed:
:required:user-valid:user-invalid:focus:focus-visible::placeholder
Here’s an example of changing styles based on state in theme.json:
{
"version": 3,
"styles": {
"elements": {
"textInput": {
"border": {
"color": "var(--wp--preset--color--contrast)"
},
":focus": {
"border": {
"color": "var(--wp--preset--color--accent)"
}
},
"::placeholder": {
"color": {
"text": "var(--wp--preset--color--accent-4)"
}
}
}
}
}
}
Pseudo-classes are wrapped in :where() like other element styles, but ::placeholder, because pseudo-elements aren’t valid inside :where().
Clone your own site into Playground with Reprint

Playground can now copy a live WordPress site into your browser, files and database included, using the Reprint plugin. This makes it easy to do things like check a plugin update, try out a design change, or reproduce a bug without changing things on your live site.
Try the public demo site, which needs no account or key if you don’t want to use your real data for a first test.
To clone your own site, install and activate Reprint on it. Then choose New Playground Clone a live site in Playground and enter the site’s address. Playground gives you a migration key, which you paste into Tools Reprint Server on the live site to authorize the copy. Entering a URL alone doesn’t grant access to anything.
Some limits to keep in mind:
- The browser import currently tops out at 2 GiB of files and database data.
- Keep the tab open until the copy finishes; closing or reloading it loses an unfinished copy.
- Playground isn’t your host’s environment, so some plugins and external services behave differently.
- The copy can contain user data and plugin credentials, so clean it up before you share an export.
For larger sites, the Reprint Handbook shows how to copy a site to your own machine from the terminal, using SQLite or MySQL.
Beyond WordPress, Joomla Playground is an early community project that runs Joomla in the browser on the same @php-wasm packages and the wordpress/mysql-on-sqlite library. This has already uncovered SQL compatibility gaps that could become regression tests for that library, along with ideas for faster browser saves.
And if you missed it last month, the Email tool captures the emails your plugin sends so you can inspect them without delivering them.
Want more?
Releases and schedules
- WordPress 7.2 Beta 1, Beta 2, Beta 3 (shipped with 7.1.4), Beta 4, and Beta 5 are out. The full schedule is on Make/Core.
- What’s new in Gutenberg 24.2 and 24.3.
- The release roadmap survey is open through November 16.
Editor and admin
- The Updates screen lists translation updates individually, so you can install them selectively.
- Notes moved into a margin beside the canvas and gained emoji reactions.
- Save and autosave failure notices now include details and a copy button.
- Plugin sidebars moved into a new Panels submenu in the editor’s Options menu.
- The Media inserter was rebuilt on a DataViews grid.
- Exploring a design for Feature Notifications is open for feedback.
APIs and data
- The
wp_kses()move to the HTML API, covered last month, is now in trunk (#66208). If you sanitize HTML and compare the result, test against Beta 5. - Both
getBlockSupport()andhasBlockSupport()accept a feature path array. - The Fields API now has a server-side registry and REST route.
- The Icon block’s
iconattribute supports block bindings.
Components and UI
- Emotion is fully removed from
@wordpress/components. - Both the
BadgeandTipcomponents are deprecated. - The
RangeControlcomponent has a newsizeprop. @wordpress/uialso added some new components:
Themes and blocks
- Design tool consistency work continued in Gutenberg 24.2 and 24.3, which included minimum width and height on about 40 blocks, shadow, duotone, background image, and writing mode support.
- Navigation Link hover, focus, and active states can be styled in Global Styles.
- Rich text formatting now works across multiple selected blocks.
- The Columns block’s column count slider was removed.
theme.jsonvalues of unexpected types are ignored instead of causing fatal errors.- Ipsum, the new default theme, received accessibility and RTL refinements in Beta 4.
Tooling
- Gutenberg development now requires Node.js 22.
wp-scriptsend-to-end tests run against the configured wp-env test environment.wp-envcan choose a MariaDB version.
Props to @psykro and @welcher for feedback and review on this post.





