WordPress 7.2 is scheduled for December 8, 2026, with Release Candidate 1 due on November 17. Beta 1 landed on October 20, which means the feature set is now mostly fixed. If you build or maintain WordPress sites for clients, the next few weeks are the time to test, not the week of release.
Here is a short, practical testing list.
1. Spin up a test site in minutes
You do not need to touch a live site to test the beta. Pick one:
- WordPress Playground runs a full WordPress install in the browser. Nothing to host, nothing to clean up.
- wp-env or a local stack if you want to test your own theme and plugins with real data.
- WP-CLI on a staging copy:
wp core update --version=7.2-beta1
- The WordPress Beta Tester plugin on staging: Tools, Beta Testing, choose Beta/RC Only, then update from the Updates screen.
2. Check the changes most likely to affect client sites
Admin icons. Dashicons are being replaced with SVG icons in the admin bar and menu. If a plugin or custom admin screen relies on Dashicon classes or styles, look at it now.
The Secrets API. WordPress is getting a standard, encrypted place for plugins to store API keys and credentials, with WP-CLI support first and a management screen planned later. If you maintain plugins that store keys in options, this is worth reading up on before your users start asking.
HTML API hardening. Markup processing is getting safer and stricter. Custom blocks or filters that do string surgery on HTML deserve a quick regression test.
Media changes. The media inserter has been redesigned, crop lineage is tracked and some image processing moves to the client. If you ship an image optimisation workflow, make sure images are not processed twice.
Design tools. Form element styling in Global Styles, text shadows, responsive style controls and inherited values in the block inspector. Great features, but check that your theme's own form styles still win where they should.
3. Look at Ipsum, the new default theme
7.2 ships a new default theme called Ipsum. It is a minimal block theme built as a blank canvas, and it ends 16 years of year-based default theme names. Existing sites keep their current theme after updating, so nothing changes for your clients automatically. It is still worth a look as a lightweight base for simple builds.
We wrote a full breakdown here: Ipsum: WordPress 7.2's New Default Theme Explained.
4. Run a boring, reliable checklist
- Turn on
WP_DEBUGandWP_DEBUG_LOGon staging. - Check Site Health after the update.
- Click through forms, checkout, search and login.
- Watch the browser console and the PHP error log.
- Test as an editor and a shop manager, not just as an admin.
- Report core bugs on Trac and editor bugs on the Gutenberg GitHub repo.
5. Plan the live update around the holidays
December 8 lands in peak shopping season in the US, UK and Australia. For WooCommerce and lead generation sites, it is worth scheduling the live update for a quieter week, ideally after the first minor release, with a full backup taken first.
For the full list of what landed in Beta 1 and what was pushed back, see our post: WordPress 7.2 Beta 1: New Features You Can Test Now.
Written by the team at Web Brick Studio, a WordPress, Shopify and UI/UX design agency working with small businesses in the US, UK and Australia.
Top comments (0)