WordPress and WooCommerce
Check WordPress and WooCommerce after a PHP update
Confirm which PHP build serves your live website, then test the tasks customers use. Site owners can gather website details while their host checks the server.
In this article
Read PHP details from the live site
Open Tools → Site Health → Info → Server in the intended WordPress environment. Save PHP version and PHP SAPI, where shown, with the domain and time. SAPI names the interface through which PHP handled the request.
For a store, compare WooCommerce → Status → Server environment → PHP version. A staging report describes staging. A terminal's php -v describes its command-line executable. Keep those records separate. See WordPress Site Health and WooCommerce System Status.
One page request cannot inventory every server behind a domain. Ask the host to account for other backends and separate PHP used by scheduled jobs.
Ask the host to identify the build
A provider can add a security fix without changing the short PHP number. Request the supplier, complete package or private-build identifier, relevant advisory, and confirmation that old PHP workers were replaced.
Please confirm which PHP build serves [domain] in [live or staging]. Site Health reports [version and SAPI] at [time and timezone]. Which advisory covers that build? Have all servers and PHP workers for this site received it? Please identify separate scheduled-job PHP and any remaining action for us.
This is a request template. For PHP2Shell, name CVE-2026-109618 and CVE-2026-109619. Keep the host's answer about your account alongside its general status announcement.
Record panel settings before changing them
| Panel | Location | Record |
|---|---|---|
| cPanel | Software → MultiPHP Manager | Domain, version, inheritance and PHP-FPM state |
| Plesk Obsidian | Websites & Domains → domain → PHP settings | Version and handler |
| MyKinsta | Site and environment → Tools → PHP settings | Live or staging environment and selected version |
Your host may limit these controls. CloudLinux PHP Selector can also affect cPanel domains. When values disagree, ask which control governs the domain. Documentation: cPanel, Plesk and Kinsta.
Before a live branch change, confirm a complete backup, an isolated restore test, recovery access outside WordPress and a plan for orders created after the backup. A panel selection alone does not identify the full security build.
Test customer tasks on staging
Use a protected copy with the intended PHP build, theme, plugins and custom code. Protect customer data and isolate email, fulfillment, accounting and stock synchronization before creating orders. Gateway test mode does not disable other integrations. WooCommerce's test-order guidance.
| Task | Expected outcome |
|---|---|
| Find and select a product | Correct variation, price and availability |
| Change cart quantity and apply a coupon | Expected subtotal and discount |
| Complete a sandbox checkout | Correct shipping and tax; matching test order and gateway transaction |
| Use a documented decline case | Clear error and expected order/payment state |
| Deliver a test order | Expected test email, download or sandbox fulfillment |
| Use an account and scheduled task | Correct order history and background action outcome |
For WooPayments, enable test mode under Payments → Settings on staging and use its documented test cards. Compare Orders with Payments → Transactions. Follow the instructions for your actual gateway. WooPayments testing.
Review WooCommerce → Status → Logs and Status → Scheduled Actions after each test. Examine failed actions individually before retrying them. Some send messages or perform financial tasks. Scheduled-action documentation.
For a site without a store, choose equivalent real tasks: submit a form to a test inbox, sign in with a test account or upload a permitted sample file.
Close the update with completed checks
After production changes, repeat the live runtime check and approved read-only tasks such as product browsing, cart display and account access. Keep payment tests on staging unless the owner separately approves a live test.
Record environment, time, expected outcome, actual outcome and relevant order or error reference for each test. Attach the host's build confirmation. Keep untested live payment behavior and unresolved background failures visible.
If something broke, give the host and developer the failed request and change time. The recovery guide helps separate connection problems from application errors.
Questions about a host's PHP update
Do I need SSH access or another plugin?
An authorized administrator can usually start with Site Health and WooCommerce Status. If these screens are unavailable, ask the site or network administrator for the fields.
Should I post the full status report?
Start with relevant runtime fields and redacted errors. The full report exposes more about your plugins and configuration than a version check needs.
Who repairs a plugin failure?
A developer or plugin supplier diagnoses application compatibility. The host confirms PHP, settings and extensions. Agree ownership before both parties make changes.
What does cPanel's Inherit setting mean?
PHP selection can come from directory configuration or the server default. Ask your host for the effective value, including how PHP-FPM affects available options.
Why are PHP settings missing in Plesk?
Available controls depend on your subscription, operating system and installed handlers. Ask the host which changes your plan supports.
Can I use a real card and refund myself?
Use the gateway's test mode on staging. WooPayments warns that live purchases charge money and refunded test purchases do not return transaction fees.
What if we have no staging site?
Ask for a protected copy with test integrations. Meanwhile gather runtime details and check read-only live behavior. Leave payment testing recorded as incomplete.
Should I copy staging's database to the live store?
A PHP switch does not require replacing customer records. An older database can erase later purchases. Use a deployment plan that preserves live data.
Sources
If the host gives you an older-looking build, learn how to check vendor fixes and running PHP.