Article WordPress

WordPress 7.2 before release: what developers should test right now

WordPress 7.2 is still in RC, which makes this the right time to test plugins and themes against the Secrets API, SVG admin icons, Interactivity API changes and routing updates.

Hamid Aarab Senior WordPress and WooCommerce Backend Developer
Published
Reading time
2 min read

Hamid Aarab November 22, 2026 2 min read

Terminal-style WordPress 7.2 RC cover with a developer test checklist
Contents (6)

As of November 22, 2026, WordPress 7.2 is not final yet. RC2 shipped on November 18 and the final release is planned for early December. This is the useful window for plugin and theme developers: test now, while regressions can still be found before users upgrade.

1. Treat the Secrets API as an architectural change

WordPress 7.2 introduces a standard Secrets API for credentials such as external API keys. Instead of every plugin inventing its own option-storage pattern, core provides a contract for setting, retrieving, deleting and rotating secrets, while hosts can replace the storage backend.

$secret = wp_get_secret( 'my-plugin/api-key' );

if ( is_wp_error( $secret ) ) {
    return '';
}

$key = $secret ? $secret->reveal() : '';

If your plugin stores credentials, design the migration now. Do not rush a production migration against an RC build; verify the final API once 7.2 ships.

2. Admin icons are real SVG elements

WordPress 7.2 moves admin-bar and menu icons toward inline SVG. CSS that assumes a Dashicons glyph in ::before may no longer behave the way you expect. Test custom admin menus, CPT icons and toolbar nodes on both 7.1 and 7.2.

3. Interactivity API gets richer navigation state

The release includes data-wp-html for explicitly trusted HTML and new navigation state that exposes whether client-side navigation is in progress and which element initiated it. Interactive blocks should be tested for transitions, focus, loading state and keyboard behavior.

4. Do not ignore the new random-content routes

The new random-content routing can interact with custom rewrites and pre_get_posts callbacks. If you run complex query filters or custom public post types, make sure random requests do not accidentally inherit logic intended for archives or search.

5. My compatibility checklist

  1. Use a clone or staging site; do not install the RC on production.
  2. Enable WP_DEBUG logging and exercise the critical plugin/theme paths.
  3. Inspect custom admin screens, menu icons and meta boxes.
  4. Test blocks and Interactivity API flows with keyboard navigation.
  5. Document migration and rollback if you store secrets.
  6. Repeat the suite against the final 7.2 build before updating Tested up to.

A release candidate is for finding regressions, not merely for bumping a compatibility header.

Sources

$ ./request_review

Facing the same problem in your own store?

Senior WordPress and WooCommerce backend engineering for complex production problems.

Request a Technical Assessment

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *