My Site Broke After a PHP Upgrade: How to Fix It

Why did my site break after a PHP upgrade?

Almost always because a plugin, theme or piece of custom code was written for an older PHP and does not work on the new one. PHP removes or tightens old behavior between versions. The code that relied on it now fails, and WordPress shows an error or a blank page instead.

How do I get my site back online right now?

Switch PHP back to the previous version. In most hosting panels, such as cPanel, this is a single dropdown labeled PHP version or MultiPHP Manager. Choose the older version, save, and reload your site. Most outages end within a minute.

That gets you online, not safe. If the old version is 8.1 or older, it no longer gets regular security updates, per the PHP 2026 news page. Treat the rollback as a pause, then fix the cause.

Why do I get a white screen after updating PHP?

A white screen usually means a fatal error that WordPress is hiding from visitors. The error is real, but the setting that hides it is a normal safety default. WordPress may also show a message saying the site is experiencing technical difficulties, and send a recovery link to the admin email.

Check that inbox first. The recovery link often lets you log in and deactivate the broken plugin.

How do I find which plugin is causing the fatal error?

Read the error log. It names the file that failed, and the folder name in the path tells you which plugin or theme it is. If you cannot reach the log, rename the plugin folders one at a time to find the culprit.

• • Check the host's error log in the hosting panel, usually under Logs or Metrics.
• • Look at the file path in the newest error, such as wp-content/plugins/name.
• • Rename that plugin's folder through File Manager or FTP to deactivate it.
• • Reload the site. If it returns, you found the cause.
• • Repeat if the error moves to a second plugin.

What do I do if my theme is abandoned and will not run on new PHP?

You have three options, and the right one depends on how much custom work sits in the theme. Check the theme's last update date first, because anything not updated in a year or more is a warning sign. The table compares the options, when each fits, and what to watch out for.

Abandoned plugins follow the same logic. Replace them when you can, because an unmaintained plugin is also a security risk. Our WordPress security service covers that review.

Could the break mean my site was hacked instead?

Rarely, but it is possible. A site that broke at the exact moment you upgraded PHP is almost certainly a compatibility issue. If you also see spam pages, unknown admin users or redirects, treat it as a possible compromise. The php2shell flaw was added to the CISA exploited list on October 26, 2026, per the CISA KEV feed.

Our explainer covers it: php2shell: What It Means for Your Website.

How do I upgrade PHP again without breaking the site?

Test on a staging copy before touching the live site. A staging copy runs on the new PHP while the real site stays untouched, so every failure happens in private. Fix each one, repeat the test, and only then switch.

First, run the free PHP version checker to confirm what the live site runs. Then ask your host for a staging tool or a developer for a copy. The planning side is covered in My Host Says Upgrade PHP.

Can Cuanto Labs fix a site that broke after a PHP upgrade?

Yes. We roll back if needed, find the failing plugin or theme, fix or replace it on a staging copy, and switch again with a rollback ready. Our PHP upgrade service starts with a $295 PHP Health Check, and a standard WordPress upgrade is $3,500 with a 30-day fix of regressions. Stores are $4,500.

We cannot promise that every old plugin can be saved. If one cannot, we tell you what a replacement involves before we change anything.

How can I prevent this from happening again?

Test every PHP change on a copy first, keep plugins and themes updated, and remove ones you no longer use. Each unused plugin is one more thing that can fail on a new PHP version, and one more thing attackers can target. A short review twice a year catches most problems before they cause an outage.

If you would rather not manage this yourself, our website care plans include routine version checks and testing before changes go live.

What is the next step?

Roll back to get online, then book the fix instead of leaving the site on an old version. Book a call and send us the error message or a screenshot. We will tell you which plugin or theme is the likely cause and what a safe second attempt looks like.

This article is general information, not legal or compliance advice. Written by Eliran Yihye, founder of Cuanto Labs, on October 27, 2026.