WordPress 7.2 is scheduled for 8 December 2026: Beta 5, released on 10 November, announces the resolution of all known core compatibility issues with PHP 8.6. For your SME, we believe the priority is to prepare tests of the functions essential to your business, keeping this test version away from the public site.
WordPress 7.2: what really changes
The official WordPress announcement concerns the core of the software. It does not guarantee that the plugins, the theme or developments specific to your business will work with PHP 8.6. The release schedule remains provisional.
Two questions therefore need separate answers: does your site work with the next version of WordPress, and then with the PHP version being considered? We must be able to specify the combinations tested before proposing an intervention.
Beta 5 also adds email notifications when application passwords are created and improves, among other things, keyboard navigation in the admin bar. If these functions apply to you, the tests will include receiving the notifications and the usual tasks of the person who publishes your content.
For an SME in French-speaking Switzerland, checking the journeys that matter

A request that is sent but never received can matter more than a visual defect. We therefore start with the actions your business depends on: receiving a form with an attachment, recording an appointment or processing an order.
For a shop, the check runs from choosing the product through to processing the sale. The WooCommerce update guide recommends checking in particular the cart, payments, delivery, taxes and emails. If you offer TWINT, this payment method is part of the tests, depending on what the installed module allows.
The person who handles enquiries or sales needs to take part. They know what information makes an enquiry usable and can confirm that an order arrives with the right contact details, the right product and the expected status. When management software receives this data, the checks continue in that tool.
The user journeys should also be tried on both phone and computer. The goal stays practical: can your customers complete what they set out to do, and can your team take over from there?
Our view: prepare a decision, do not chase a date
The announcement is encouraging, but it is not enough to authorise an update of your installation. We prefer a decision based on the test results and the remaining uncertainties.
An order that cannot be placed should block going live. A minor visual shift can be arbitrated separately. This classification is prepared with you, before the tests, to avoid discovering at the last minute that we do not share the same criteria.
November can be used to establish this baseline. If the checks reveal a broader need for change, our support in web design makes it possible to place these adaptations within the project as a whole. The date of the intervention remains tied to the actual release schedule and to the results obtained.
Three points to prepare before any intervention
-
An inventory and priorities. We list WordPress, the theme, the plugins, PHP and custom developments, with their use and the person responsible. Compatibility has to be qualified: confirmed by the publisher, verified on the test copy or still to be clarified. You validate the essential user journeys and the defects that would prevent going live.
-
A representative test copy. The tests must reuse your content, settings and useful connections, with differences from the public site clearly identified. Emails go to test addresses, payments use the mode intended for this purpose and external actions are neutralised. The access rights and customer data needed are kept to a minimum. Each test records the expected result, the observed result and any correction.
-
An organised rollback. We check the backup of files and database, whether it can actually be used, and who is able to restore the previous PHP version. For an online shop, recent orders must be preserved: an old test copy must not overwrite them. The person responsible for the decision and the checks after restoration are defined before the intervention.
The useful deliverable this week comes down to three elements: a test plan, a named person in charge and a date to review the results together.




