WordPress 7.2 Beta 2 Is Out: What to Test Before December 8
The admin no longer bundles its scripts, and that change can trip up old firewall rules and image plugins.
WordPress 7.2 Beta 2 came out on October 27, and the final release of the next big version is set for December 8. You’ve got about five weeks to test your themes and plugins.
Keep it off your live sites, though, because WordPress.org says the beta is for testing and development only, and that goes double for any client site you look after.
Use a staging copy, a local site or WordPress Playground.
What Beta 2 adds
The Beta 2 post lists more work across the administration experience and developer APIs:
- the Abilities API, with content querying, capability requirements, schemas and permissions
- server-side registration for DataViews and DataForm, so developers can extend admin screens
- REST API changes and admin asset loading
- the transition to modern SVG icons throughout WordPress administration
So why care about Abilities? According to the Beta 1 post, the API gives integrations, automation and AI-powered tools a more consistent foundation, and the AI team’s plan wants a useful set in core for 7.3.
What’s already in 7.2
The Beta 1 post set out the bigger list for you:
- new text shadow controls
- gallery columns, cropping and aspect ratios that change with screen size
- image processing in your browser before upload, in the Media Library
- emoji reactions on Notes
- an “On This Day” dashboard widget
- an admin that prefetches the screen you’re likely to open next
For developers, a new Secrets API handles credentials like API keys, with encryption at rest, rotation and pluggable storage.
Will your old firewall rules break?
They might. Dr. Web’s look at the admin changes says load-scripts.php and load-styles.php now return a 410 Gone status, and the admin loads each file on its own.
Then the CONCATENATE_SCRIPTS line in your wp-config.php does nothing anymore.
Why drop bundling? Dr. Web says developers blamed it for bugs, and it opened the door to a 2018 denial of service flaw, so any rule that mentions those two files needs a look.
The dates
Here’s the official 7.2 schedule from Make WordPress Core, all at 15:00 UTC:
| Milestone | Date |
|---|---|
| Beta 3 | November 3 |
| Beta 4 | November 10 |
| RC 1 | November 17 |
| RC 2 | November 24 |
| RC 3 | December 1 |
| Final release | December 8 |
Why it matters
Most 7.2 changes won’t touch your visitors. But the admin changes can, especially on a site with years of custom rules piled up in a CDN or a security plugin.
Still, image processing is the one I’d test first.
Dr. Web notes that two image hooks don’t fire when your browser does the work, so check your image optimization plugin on a test copy before a client’s media library depends on it.
That said, if you run a Content Security Policy, add blob: to worker-src, or the work falls back to your server.
I’d clone one busy site to staging this week. Install the beta with the WordPress Beta Tester plugin or WP-CLI, then try your uploads.
Something breaks? Share it in the Alpha/Beta area of the support forums.
Common Questions
When is WordPress 7.2 released?
WordPress 7.2 is scheduled for December 8, 2026, at 15:00 UTC. Release candidates are planned for November 17, November 24 and December 1, with two more betas on November 3 and 10.
Is it safe to install WordPress 7.2 Beta 2 on a live site?
No. WordPress.org says the beta is for testing and development only. Use a staging copy, a local site or WordPress Playground.
What happens to load-scripts.php in WordPress 7.2?
It stops bundling admin scripts. According to Dr. Web, load-scripts.php and load-styles.php return a 410 Gone status, so firewall or CDN rules that mention them should be reviewed.
