WordPress 7.2 is due on December 8. The release posts lead with a new default theme, text shadows and emoji reactions on editorial notes. That’s fine, but if you run a business site, especially a classic one, the changes that matter are further down the list, or not in the announcements at all. I installed Release Candidate 2 and read the code. Here’s what I’d want to know before the update lands.
Where it stands
7.2 is at Release Candidate 2 (November 18). Features are frozen, and from here on it’s bug fixes. Release candidates are not for production: test on a staging copy.
wp core update --version=7.2-RC2
Run that on staging only. Or use WordPress Playground in a browser, with nothing to install.
What’s new for editors
The headline features, briefly:
- Ipsum, a new default theme.
- More responsive design controls, including per-device Gallery columns, cropping and aspect ratios.
- Global Styles improvements: a filter that finds blocks with custom styles, inherited values shown in the block settings, and text shadows.
- Notes move onto the editing canvas, with emoji reactions and a minimized mode.
- Navigation can be edited from the Site Editor sidebar.
- An “On This Day” dashboard widget that shows what you published on this date in earlier years.
- Admin icons move from Dashicons to the WordPress icon library.
Most of that lives in the block editor. If your site runs the classic editor, you’ll notice the icons, the dashboard widget and not much else.
What matters if you run the site
1. load-scripts.php is retired
For years, the admin combined its JavaScript and CSS into single requests through wp-admin/load-scripts.php and load-styles.php. In 7.2, assets load as individual files so browsers can cache them, with prefetching for the next admin screen you’re likely to visit. Both files now just return 410 Gone without loading WordPress.
That’s good news for security as well as speed. load-scripts.php was the target of a well-known denial-of-service technique in 2018, because one request could make the server combine every script in core. Now a request costs nothing. But if you have server rules, a CDN configuration or a security plugin setting that mentions these files, you can clean it up. If you have custom code that links to them, it will stop working.
2. Every site gets a /random/ URL
7.2 adds random content redirects: example.com/random/ sends visitors to a random post, and example.com/random/category/news/ to a random post in that category. It’s on by default.
The implementation is careful. It picks random post IDs instead of making the database sort every post, and it skips feeds, sitemaps and search. But it’s still a new public URL on every WordPress site, and every request to it is a fresh random pick, so it’s work your page cache can’t do for you. Crawlers will find it. If you don’t want it, one line turns it off:
add_filter( 'wp_enable_random_content_redirect', '__return_false' );
On a corporate site, I would. Random discovery suits a blog with years of archives, and few B2B visitors go looking for a random case study.
3. Images get processed in the browser
7.2 extends client-side media processing to the Media Library. Images can be resized, compressed and converted in the visitor’s browser before upload, instead of on your server. That helps on hosts with weak image libraries. It also means the images your server receives may already be processed. If you run an image optimization plugin, or have a pipeline that expects originals, test an upload or two on staging and compare the results.
4. Classic editor sites: test the editor
Here’s one that isn’t in the announcements. The classic editor runs on TinyMCE, and WordPress used to load it as one bundled file, wp-tinymce.js. In 7.2 that bundle is no longer registered. TinyMCE loads as its core file plus the plugins it needs. The code keeps the old wp-tinymce handle working, so most sites won’t notice. But if you run the Classic Editor plugin, or a plugin that adds TinyMCE buttons or customizes the editor, open the editor on staging and try your toolbar before you update production.
5. The Secrets API isn’t in the release candidate
The Beta 1 announcement highlighted a new Secrets API: a standard way for plugins to store API keys and tokens with encryption at rest and rotation. For a security-minded site, that was the most interesting item on the list. I searched the RC 2 code and couldn’t find it. It looks like it didn’t make the cut for 7.2. Don’t plan around it until a release actually includes it.
6. Smaller things worth a note
- PHP: the minimum is still PHP 7.4, and 7.2 adds PHP 8.6 compatibility fixes. Running the oldest supported version is still a bad idea.
- Abilities API: expanded, to give integrations and AI tools a standard way to query WordPress data. Worth knowing about, given how fast AI plugins are becoming a new front door.
- Bundled libraries: PHPMailer, Requests, getID3 and sodium_compat are all updated.
- Translation updates get better management in the admin.
How I’d handle the update
- Now: copy production to staging and update it to RC 2. Click through the admin, the editor and your forms. Upload an image. Check your error log.
- Before December 8: decide about
/random/, and clean up any rules that referenceload-scripts.phporload-styles.php. - On release: 7.2 is a major release, so automatic background updates won’t install it unless you’ve opted in. Give it a few days, watch for 7.2.1, then update production the way you always do: backup first, then update, then verify.
Security releases are different. When 7.2.x security releases ship, install those quickly, as with 7.1.5.
My take
7.2 is a solid, unexciting release, and that’s a compliment. Its best change for site owners, individual asset loading, will mostly go unnoticed except as a faster admin. The changes worth acting on are the quiet ones: a new public URL that’s on by default, a retired endpoint, and an editor change that only classic sites will feel. Release notes are written for the people building the features. The question for the people running the site is always the same: what changed that I didn’t ask for? With 7.2, the answer is short, and now you have it.