Upgrading PHP on a WordPress or WooCommerce site without breaking it

Quick answer: Upgrading PHP on a WordPress or WooCommerce site is usually straightforward if you do it in the right order: back up everything, update your plugins and theme first, test the new PHP version on a staging copy (never live), check that checkout, forms and logins still work, then switch the live site over at a quiet time with a rollback ready. The thing that breaks sites isn’t PHP itself — it’s an abandoned plugin that never kept up.

“Just change the PHP version” sounds like a one-click job, and sometimes it is. But on a real business site — especially a WooCommerce store with plugins, a payment gateway and an accounting sync — a careless switch can take down checkout at the worst possible moment. Here’s how to do it so customers never notice.

First, why bother: WordPress recommends PHP 8.3 or greater and WooCommerce recommends the same (tested up to 8.4). Older versions still run, but they age out of security support — see our guide to supported PHP versions. A newer version is safer and usually faster.

Step 1: Back up — and confirm the restore

Before touching anything, take a full backup of both the files and the database, and confirm you can actually restore it. An untested backup isn’t a safety net; it’s a hope. This is the step people skip and regret.

Step 2: Update plugins, themes and core first

This is the real secret to a painless PHP upgrade. The vast majority of “the upgrade broke my site” stories trace back to an out-of-date plugin or theme, not to PHP. Newer PHP versions remove or tighten things that old code relied on, and well-maintained plugins have already been updated to cope — abandoned ones haven’t.

So, in order:

1. Update WordPress core.
2. Update every plugin.
3. Update the theme.
4. Make a note of any plugin that hasn’t had an update in a year or two — those are your likely trouble spots, and sometimes the honest answer is to replace them.

Step 3: Test on a staging copy, not live

Never switch the PHP version on your live site to “see what happens.” Create a staging copy — many hosts offer one-click staging — and switch that to your target version (8.3 or 8.4). Your live site keeps serving customers on the old version while you test.

Step 4: Exercise the things that earn you money

On the staging copy, don’t just load the home page and call it done. Actually use the site the way customers and staff do:

• Checkout, end to end — add to cart, apply a coupon, complete a test order, confirm the payment gateway responds.
• Forms — enquiry, contact, booking.
• Logins — customer accounts and the admin.
• Integrations — if the store syncs to accounting or shipping, test that too. A broken WooCommerce-to-Xero or MYOB sync can be silent and expensive. (This is exactly the kind of thing covered in the integration testing most teams skip.)
• The error log — read it. New PHP warnings and deprecation notices show up here first.

Step 5: Go live, with a rollback ready

Once staging is genuinely clean, switch the live site to the new PHP version — at a quiet time, not during your busiest trading hour. Immediately re-test the key flows on live, and keep the ability to switch straight back to the previous PHP version if something only shows up under real traffic. If you’ve done steps 1–4 properly, this is usually uneventful.

When to get help

If the site is a busy store, if it has a lot of plugins, or if an old plugin with no replacement is the thing standing in the way, it’s worth having someone run the upgrade for you — on staging first, with the testing and rollback handled. That’s routine work for us across WordPress, WooCommerce and ecommerce builds. Get in touch and we’ll do it the careful way.

Common questions

Will upgrading PHP break my WordPress site? It can, but the usual cause is an outdated or abandoned plugin or theme, not PHP itself. Updating everything first and testing on a staging copy prevents almost all of the breakage.

Do I need a staging site to upgrade PHP? It’s strongly recommended, especially for WooCommerce or any site with plugins. Staging lets you find and fix problems where customers can’t see them. Many hosts provide one-click staging.

What if a plugin isn’t compatible with the new PHP version? Check for an update first. If the plugin is abandoned, the safer path is to find a maintained replacement rather than hold your whole site back on an unsupported PHP version for the sake of one extension.

Can I roll back if the upgrade causes problems? Yes — switching the PHP version back to the previous one is usually quick, which is why you keep that option open when you go live. Treat it as a stop-gap while you fix the real cause, not a permanent home.