WordPress 7.2 Arrives in December: Preparing a Small Business Site
The next major WordPress release, version 7.2, is scheduled for 8 December 2026, according to the WordPress 7.2 Beta 5 announcement. For a small business, December is an awkward month for site changes, because it is often your busiest. The sensible approach is to prepare now, let the release settle for a short while, and update on a quiet day with a backup ready.
What is in the release
The beta announcement gives a flavour of the refinements made during testing. Among them: email notifications when application passwords are created, keyboard navigation improvements in the admin toolbar, accessibility work on Visual History, MP3 upload fixes, and a new default theme called Ipsum with better focus indicators and view transitions that respect reduced-motion settings. The post also says PHP 8.6 compatibility is fully addressed as of Beta 5.
For most small business owners, none of that changes how you run the site day to day. The value of updating lies mainly in staying on a maintained version that receives fixes, rather than in any single feature.
The announcement is also clear that beta versions should not be installed on production or mission-critical sites. If you are curious, try the beta on a test copy, never on the live shop.
Do not update on release day
Major releases are well tested, but the wider world of themes and plugins catches up over the following days. For a site that takes bookings or orders, there is little to gain from being first. A reasonable pattern is:
- leave automatic minor and security updates switched on, since those are small and important;
- wait until a few days after a major release, by which time plugin developers have usually posted compatibility updates;
- pick a quiet slot, which for many shops in December means early on a weekday morning;
- avoid the last few days before Christmas altogether unless there is a security reason.
Preparation you can do now
Check the PHP version
WordPress currently recommends PHP 8.3 or greater, and the PHP project's support schedule shows PHP 8.2 losing security support on 31 December 2026. If your site is still on 8.2 or older, sort that out first, as a separate job, so you are not changing two things at once. We cover how in PHP 8.2 reaches end of life.
Review the plugins
Go to the Plugins screen and look at each one honestly. Do you still use it? When was it last updated? Is there a premium licence that has lapsed, meaning you are not getting updates at all? Remove what you do not need. Every unused plugin is one more thing that can conflict with an update or carry a security flaw.
Know your theme
If your site uses a commercial theme or a page builder, check the developer's site or changelog for notes about 7.2 compatibility nearer the release. If a developer built a custom theme for you, ask whether they plan to test it.
Confirm backups and restore
Backups are only useful if you can restore them. Check where yours are stored, how far back they go, and whether your host can roll back a site in one step. Make a fresh backup immediately before updating.
Update day
- Take a backup and note the time.
- Update plugins and theme first, one at a time if you have only a few, so you can tell which caused any problem.
- Update WordPress core.
- Clear any caching plugin or host cache.
- Walk through the site: home page, a service page, the contact form, the basket and checkout if you sell online, and the editor in the admin area.
- Send a test enquiry and confirm it arrives.
If something breaks and is not quickly fixable, restore the backup and contact your developer or the plugin's support. A rolled-back site is better than a broken one in mid-December.
A word on accessibility
Several of the 7.2 changes, such as clearer focus indicators in the new default theme and better keyboard movement around the admin toolbar, are about people who do not use a mouse. That is a useful prompt to check your own front end in the same way. Put the mouse aside and press Tab through your home page and contact form. Can you always see where you are? Can you reach and submit the form? Does a menu open and close from the keyboard? If anything gets stuck, note it for your developer. Our guest piece on specifying button states before sign-off explains why a visible focus state should be designed rather than left to chance, and fixing it helps every visitor who uses a keyboard, switch device or screen reader.
If someone else looks after the site
Many small firms pay a developer or agency for maintenance. Ask them three simple questions: when will you apply 7.2, how will you test it, and how quickly can you roll back if needed? If you do not have a maintenance arrangement and are not comfortable doing this yourself, a one-off update and health check before the end of the year is a modest cost.
Use the moment for a wider tidy
An update is a natural point to look at the site with fresh eyes. Are the opening hours current? Do service pages still describe what you sell? Are there old announcements still showing? Our guest contributor's notes on announcement cards with a clear expiry are handy for that last one. A maintained site is mainly a matter of small habits repeated, and the start of a new year is a good time to set them.