> Every Protuno article: https://protuno.com/blog.md · Site map for AI agents: https://protuno.com/llms.txt

# WordPress 7.2: What’s New, and How to Test Your Site Before You Update

- Date: 20 November 2026
- Page: https://protuno.com/blog/wordpress-7-2

WordPress 7.2 is scheduled for release on 8 December 2026. Release candidate 1 came out on 17 November, and the release brings a new default theme called Ipsum, a modernised admin with SVG icons and faster navigation, and a new Secrets API for storing API keys safely.

This post is about WordPress 7.2, the next version of WordPress. It is not about PHP 7.2, an old PHP version.

> **At a glance**
> 
> 
> 
> **Release date:** 8 December 2026 (scheduled). RC1 shipped 17 November 2026.
> 
> **Biggest changes:** the Ipsum default theme, more responsive design and Gallery controls, a faster admin, Canvas Notes, and the Secrets API.
> 
> **Should you update on day one?** On a business site, test first on a copy, then update.
> 
> **Plugins:** three days after RC1, only 3 of the 50 popular plugins we checked said they were tested with 7.2.

> **We checked plugin readiness on wordpress.org**
> On 20 November 2026 we read the “Tested up to” value of the 50 plugins on wordpress.org’s Popular list, straight from the plugin directory. 3 declared 7.2, 42 declared 7.1, 2 declared 7.0 and 3 declared 6.9 or older. That is normal at this stage: WordPress asks plugin authors to update the value during the release candidates. It is the reason to check your own plugins before you update.

![Bar chart: of 50 popular plugins, 3 declare tested with 7.2, 42 with 7.1, 2 with 7.0 and 3 with 6.9 or older](https://protuno.com/blog/media/2026/11/wordpress-7-2-u72-tested-chart.webp)

*Our check of the plugin directory, three days after 7.2 RC1.*

## When Is WordPress 7.2 Released?

The final release is scheduled for 8 December 2026. The schedule so far:

- **Beta 1 to Beta 5**: October to November 2026
- **Release candidate 1 (RC1)**: 17 November 2026
- **Final release (scheduled)**: 8 December 2026

*From the official RC1 announcement and the Make WordPress Core 7.2 page.*

Meanwhile, keep 7.1 up to date. WordPress 7.1.5, a security release, shipped this week, and wordpress.org recommends updating to it straight away.

## What Is New In WordPress 7.2 For Site Owners

The official RC1 announcement lists these highlights:

- **Ipsum, a new default theme.**
- **More responsive design and Gallery controls,** plus improved Global Styles and typography tools.
- **Canvas Notes and collaboration.** Notes moved into a margin beside the editor canvas.
- **A DataForm block settings inspector,** a new way the editor shows block settings.
- **Faster media uploads and image processing.**
- **A modernised admin.** Admin bar and menu icons are now SVG, and admin navigation and asset loading are faster.
- **An “On This Day” widget and random post discovery.** A new `/random` address sends visitors to a random published post.
- **Translation updates you can pick one by one** on the Updates screen.
- **Accessibility, security and PHP 8.6 compatibility improvements.**

For most site owners the visible changes are the admin look, the editor tools and the new theme. Your existing theme stays active after the update. Ipsum is only used if you choose it.

## What Is New In WordPress 7.2 For Developers

The November developer roundup on developer.wordpress.org covers the changes most likely to affect plugins and themes:

- **The Secrets API.** Plugins can store API keys encrypted instead of as plain text in the options table, with `wp_set_secret()` and `wp_get_secret()`. A new `WP_SECRETS_KEY` constant in wp-config.php holds the key. New installs get it automatically, and Site Health tells existing sites how to add it.
- **SVG admin icons.** Dashicons in menus still work, but CSS that styles icons through `::before` may break.
- **Admin scripts are no longer concatenated.** `load-scripts.php` and `load-styles.php` are deprecated, and some scripts now print in the footer instead of the head.
- **Random content addresses,** with a `randomable` argument on post types to opt out.
- **Interactivity API additions,** including a `data-wp-html` directive.

If a plugin or theme you rely on styles admin icons, links to `load-scripts.php`, or expects scripts in the head, it is the first thing to test.

## Should You Update To WordPress 7.2 Right Away?

It depends on what the site does. A personal blog with a few well-known plugins can usually update within days. For a shop, a membership site or a client site, update after you have tested it on a copy. Two reasons:

- **Plugin readiness lags.** Our check found most popular plugins still declaring 7.1 three days after RC1. WordPress asks authors to update the value during the release candidates.
- **Fixes follow major releases.** Both 7.0 and 7.1 were followed by maintenance or security releases (7.0.1 and 7.1.1).

Also check whether your site updates major versions on its own. Go to *Dashboard, Updates* and read the line about automatic updates. [Our auto-updates guide](https://protuno.com/blog/wordpress-auto-updates-policy) explains how to choose a policy per site.

## How To Test Your Site Before You Update

Never test a release candidate on a live site. WordPress itself says so in every RC announcement. Use a copy.

### 1. Make A Copy Of The Site

Use your host’s staging tool, or clone the site. WordPress Playground can now copy a live site into your browser with the Reprint plugin, which is handy for a quick check (the browser import tops out at 2 GiB). [Keep staging close to live](https://protuno.com/blog/wordpress-staging-drift), or the test tells you little.

### 2. Check What Your Plugins Declare

Open *Plugins* and, for each active plugin, check its wordpress.org page for “Tested up to”. Note any plugin not updated in a year or more. Premium plugins are not on wordpress.org, so check the vendor’s changelog instead.

### 3. Install 7.2 On The Copy

Any of the 4 official ways works:

- The WordPress Beta Tester plugin, with the “Bleeding edge” channel and “Beta/RC Only” stream.
- The RC zip from wordpress.org.
- WP-CLI: `wp core update --version=7.2-RC1`
- WordPress Playground, in the browser, with nothing to install.

### 4. Click Through What Matters

Load the home page, a post, a page with forms, the checkout if you have one, and the admin screens you use daily. Log in and out. Save a post. Watch for errors, missing icons and broken admin menus. If anything breaks, switch plugins off one at a time on the copy to find which one.

### 5. Write Down What To Do On Release Day

Keep a short list: what to update first, what to check after, and which plugin to wait on. That list is your release-day plan.

## What To Do On Release Day

1. Take a full backup and check it is complete. [Here is how to check a backup](https://protuno.com/blog/wordpress-backup-verification).
2. Update plugins first, one at a time, checking the site after each. [Our safe plugin update guide](https://protuno.com/blog/wordpress-plugin-safe-update) covers the order.
3. Update WordPress itself from *Dashboard, Updates*.
4. Check your key pages and the admin again.
5. If something breaks, [get the site back first](https://protuno.com/blog/wordpress-site-down-after-plugin-update), then find the cause.

## When The Update Is Not The Problem

- **A plugin breaks after 7.2 but declares 7.2 support.** The declaration is the author’s statement, not a test of your site. Report it to the plugin author with the steps to reproduce.
- **The site breaks after a host change at the same time.** Hosts often roll out new PHP versions. Check the PHP version in *Tools, Site Health, Info* before blaming WordPress. [Our PHP guide](https://protuno.com/blog/wordpress-php-end-of-life) covers versions.
- **Only the admin looks different.** That is the new SVG icons and faster asset loading, not a fault.

## Check Readiness With A Super Agent

Protuno is Super Agents for WordPress: six AI agents you use from Claude, Claude Code, Codex or Cursor, each working from written playbooks and a Brain for each site. Wren, the Care agent, has a [Major Update Readiness playbook](https://protuno.com/playbooks/major-update-readiness) that does step 2 above for you.

![The Major Update Readiness playbook in Protuno: 2 steps, both marked only reads](https://protuno.com/blog/media/2026/11/wordpress-7-2-u72-mur-steps.webp)

*The playbook: 2 steps, both read only.*

You add one line to its instructions, “Target WordPress version: 7.2”, and ask in your AI app: “Wren, is my site ready for WordPress 7.2?” Wren looks up up to 20 active plugins and your theme on wordpress.org and compares their tested version with 7.2. The report rates the site “Not ready yet”, “Check first” or “Looks ready on paper”, with what to check first and one action for each. It only reads and starts no update.

It is honest about its limits: declared compatible only means the wordpress.org page says the plugin was tested up to that version, not that the update will go well. Premium and custom plugins are reported as not on the directory and are not scored, and inactive plugins, custom code, the host’s PHP version and plugins beyond the first 20 are not checked.

On release day, [Plugin Safe Update](https://protuno.com/playbooks/plugin-safe-update) updates plugins one at a time after a backup and checks the site after each. That one can change the site, so what it does depends on Wren’s mode on that site. Read only: no changes run. Approval mode: a run starts only when you press Approve in Protuno. Auto mode: runs start on their own, with no approval. More about [Wren](https://protuno.com/docs/super-agent-wren) and [all six Super Agents](https://protuno.com/agents), or our earlier guide to [core update readiness](https://protuno.com/blog/wordpress-core-update-readiness).

## Common Questions

### When is WordPress 7.2 released?

WordPress 7.2 is scheduled for 8 December 2026. Release candidate 1 came out on 17 November 2026. The date can move if the release team finds a serious problem, so check wordpress.org/news in the week before.

### What’s new in WordPress 7.2?

The headline changes are the Ipsum default theme, more responsive design and Gallery controls, Canvas Notes, a faster admin with SVG icons, faster media uploads, an “On This Day” widget and random post discovery, and, for developers, the Secrets API.

### Should I update to WordPress 7.2 right away?

On a simple site, usually yes within days. On a shop, membership or client site, test on a copy first, take a backup, update plugins one at a time, then update WordPress. Many plugins are still updating their “Tested up to” value.

### How do I test WordPress 7.2 before updating?

Use a staging copy or WordPress Playground, never your live site. Install the release candidate with the Beta Tester plugin, the zip, WP-CLI (wp core update - version=7.2-RC1) or Playground, then click through your key pages and admin screens.

### Is WordPress 7.2 compatible with my plugins?

Check each active plugin’s “Tested up to” value on wordpress.org, and test on a copy. Three days after RC1, only 3 of the 50 popular plugins we checked declared 7.2. A declared value is the author’s statement, not a test of your site.

## Related Reading

- [WordPress core update readiness](https://protuno.com/blog/wordpress-core-update-readiness)
- [Update WordPress plugins safely](https://protuno.com/blog/wordpress-plugin-safe-update)
- [A WordPress auto-updates policy](https://protuno.com/blog/wordpress-auto-updates-policy)
- [WordPress site down after a plugin update](https://protuno.com/blog/wordpress-site-down-after-plugin-update)

## Sources

- [WordPress.org News, WordPress 7.2 Release Candidate 1](https://wordpress.org/news/2026/11/wordpress-7-2-release-candidate-1/)
- [Make WordPress Core, WordPress 7.2](https://make.wordpress.org/core/7-2/)
- [WordPress Developer Blog, What’s new for developers? (November 2026)](https://developer.wordpress.org/news/2026/11/whats-new-for-developers-november-2026/)
- [WordPress.org News, Releases](https://wordpress.org/news/category/releases/)
- [wordpress.org plugin directory, Popular plugins](https://wordpress.org/plugins/browse/popular/) (read 20 Nov 2026)
