WordPress announced 7.2 Release Candidate 1 on 17 November 2026. It remains development software, and the announcement says to evaluate it on a separate test site rather than a production or mission-critical website. For a WooCommerce team, this is a useful point to turn a vague concern into a report a maintainer can reproduce.
Choose one task and record the starting point
Pick a task your team actually uses, such as editing a product description, replacing a product image or checking a campaign page on a phone. Write down the exact page and intended outcome before testing. A narrow question is easier to investigate than a general statement that the store looks different.
On the separate test installation, record the WordPress build, WooCommerce version, active theme and relevant extensions. Include the PHP version and browser in the private handover. WooCommerce’s update guidance recommends current backups and staging checks. Confirm who can restore the test copy and keep its external integrations under control.
Compare the same steps before and after
Save a reference for the task on the current working setup before changing the test copy. Then repeat the same steps with RC1. Keep the product, account role, browser and page content consistent. If another plugin or theme also changes, record that difference rather than attributing the result to WordPress alone.
For an editing issue, note whether the difference appears while editing, in the saved preview or on the public test page. Check the saved result after reloading. For a shopper-facing issue, include the route from the campaign page to the affected product. Record the selected variation and quantity when they affect the result, and start with the same cart contents on each comparison. That context helps the maintainer find the relevant component.
Describe the result without guessing its cause
Write short numbered steps, the expected result and the actual result. Include the time and whether the issue happens every time or only under a particular condition. A screenshot can explain a layout problem, but it should accompany the steps. Review captures and logs for customer details, access links and other private information before sharing them.
Ask your maintainer to choose the appropriate support route after reproducing the finding. The RC1 announcement points compatibility issues to WordPress support. An extension-specific problem may need its developer instead. Keep the original report and add the outcome of each focused follow-up, including a result that could not be reproduced.
Keep the test report separate from a release decision
Give the finding a named owner and a next review date. After a correction or a later candidate, repeat the original task and add the exact build tested. Mark unresolved questions clearly. Keep a dated note of which pages and tasks were actually checked, so the next person can see where testing stopped. A successful edit on one page is evidence about that task; it does not establish that every store integration is ready.
Our StoreCalm monitoring adds evidence about a configured journey to checkout. Automatic checks stop before order submission and payment. Healthy describes that run, and Inconclusive needs investigation. Keep payment acceptance and other untested workflows as separate checks. The links below explain our monitoring product and provide the free StoreCalm Connector download.
Sources and further reading
- WordPress 7.2 Release Candidate 1, announced 17 November 2026
- WooCommerce update preparation guidance
- StoreCalm guide to useful WooCommerce error evidence
- StoreCalm checkout monitoring
- StoreCalm Connector setup
- Download the free StoreCalm Connector ZIP
Sources checked on 18 November 2026.