- Find the email from WordPress titled "Your Site is Experiencing a Technical Issue": it names the plugin or theme that crashed and contains a link to recovery mode.
- No email? Turn on
WP_DEBUG_LOGand look atwp-content/debug.log. - Disable the guilty plugin by renaming its folder. The site will open again.
- Update or replace the plugin. Rolling PHP back is only good for a few hours.
You open your site and instead of the home page you see a single line: "There has been a critical error on this website". Or just a white screen. The admin panel won't let you in either. Most often the cause is the same: the PHP version on your hosting changed, and some plugin or theme isn't ready for it.
The full text of the message is "There has been a critical error on this website"; in older versions of WordPress there was just a white screen instead, the so-called "white screen of death". The meaning is the same: PHP hit a fatal error and stopped without serving the page. The good news: your data hasn't gone anywhere. Posts, pages, products and orders are sitting safely in the database. It's the code that is broken, not the content.

Why so many sites are breaking right now
On October 21, 2026 the PHP team released urgent updates 8.5.12, 8.4.27, 8.3.36 and 8.2.35. They close two critical vulnerabilities nicknamed php2shell, which let an attacker run code on your server without any login. We cover what they are and who they affect in a separate article: php2shell: what a site owner should do.
Hosting providers react in different ways. Fresh patches within the same branch (for example, 8.3.35 to 8.3.36) almost never break sites. What does break them is something else: sites that sat on PHP 7.4, 8.0 or 8.1 for years are now being moved to supported branches, because the old ones no longer get security fixes. And code written ten years ago crashes on PHP 8.
Step 1. Check the administrator's email
Since version 5.2, WordPress catches fatal errors on its own. When the site crashes, it sends an email to the administrator with the subject "Your Site is Experiencing a Technical Issue" (translated if your site uses another language). The email contains three useful things:
- the name of the plugin or theme where the error occurred;
- the error text with the file and line number;
- a link to recovery mode.
Recovery mode lets you into the admin panel as if the guilty plugin weren't there. Follow the link, deactivate the plugin named in the email, and check the site in another tab. The link is temporary, so don't put it off.
No email? Check your spam folder and remember which address is set in your WordPress settings. Often it's the mailbox of the developer who built the site several years ago. In that case, go to step 2.
Step 2. Turn on the error log
Open the wp-config.php file in the site root through your hosting file manager or FTP. Find the line define( 'WP_DEBUG', false ); and replace it with these three lines. Put them above the comment /* That's all, stop editing! */:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
The last constant matters: errors are written to a file but not shown to visitors. Now open the site again and look at the wp-content/debug.log file. If it isn't there, check the error log in your hosting panel (usually a "Logs" section or an error_log file in the site root).
Step 3. Read the Fatal error
In the log, look for a line containing PHP Fatal error. Skip the Deprecated, Warning and Notice entries for now: they clutter the log, but they don't bring a site down. A typical fatal line looks like this:
PHP Fatal error: Uncaught Error: Call to undefined function create_function()
in /home/user/public_html/wp-content/plugins/old-slider/inc/init.php:42
Look at the path. wp-content/plugins/old-slider/ means the old-slider plugin is to blame. wp-content/themes/name/ means the theme is to blame. If the path leads into wp-includes or wp-admin, the WordPress core is too old for the new PHP version and needs updating.
Step 4. Bring the site back to life
Disable the plugin without the admin panel
In the file manager, open wp-content/plugins/ and rename the folder of the guilty plugin, for example old-slider to old-slider-off. WordPress won't find the plugin and will deactivate it by itself. Don't know which one is to blame? Rename the whole plugins folder, check the site, change the name back and enable plugins one by one in the admin panel until the error returns.
Switch the theme
If the error is in the theme, rename the folder of the active theme in wp-content/themes/. WordPress will switch to a default theme if one is installed on the site (Twenty Twenty-Four, Twenty Twenty-Five and so on). The site will look different, but it will open and you'll be able to get into the admin panel.
Temporarily roll back the PHP version
Most hosting panels let you choose the PHP version for a site. Going back to the previous one is the fastest way to get the site up when you have no time at all. But a rollback is a bandage, not a cure:
- PHP 8.1 and older branches no longer get security fixes, and php2shell stays open on them;
- PHP 8.2 is supported only until December 31, 2026;
- your host may force the site onto the new version again, and everything will repeat.
A rollback buys you a few hours to calmly fix the plugin or theme. Don't stay on it any longer than that.
Update everything that is outdated
Once the admin panel works again, update the WordPress core, the theme and the plugins. Most actively maintained plugins have been compatible with PHP 8 for a long time. If a plugin hasn't been updated in several years, look for a replacement: patching someone else's abandoned code is an expensive and thankless job.
What exactly breaks in old code on PHP 8
These are the errors we see most often in the logs of sites moving off old PHP:
| What's in the log | Cause | Result |
|---|---|---|
Call to undefined function create_function() | the function was removed in PHP 8.0 | the site crashes |
Call to undefined function each() | the function was removed in PHP 8.0 | the site crashes |
Array and string offset access syntax with curly braces is no longer supported | the $str{0} curly-brace access was removed in PHP 8.0 | the site crashes |
Uncaught TypeError: count(): Argument #1 must be of type Countable|array | since PHP 8.0 built-in functions throw an error on a wrong argument type | the site crashes |
Passing null to parameter … is deprecated | since PHP 8.1, passing null to built-in functions is deprecated | only a log entry |
Creation of dynamic property … is deprecated | since PHP 8.2 dynamic properties are deprecated | only a log entry |
The first four rows are real breakages: they have to be fixed in the code or the plugin replaced. The last two are warnings about the future: the site works, but the log keeps growing, and in one of the upcoming PHP versions these places will stop working too.
How to update PHP without breaking anything
- Backup. A full copy of the files and the database before any changes. Most hosts do it with one button.
- A copy of the site. A test subdomain or staging site with the same WordPress version, where you switch on the new PHP version.
- Updates on the copy. Core, theme, plugins. Abandoned plugins get replaced.
- Testing. The home page, lead forms, cart and payment, the admin panel. The error log should have no Fatal errors.
- Switching. The same steps on the live site, in the hour with the least traffic. Keep the log on for another day.
Which version to choose? WordPress.org recommends PHP 8.3 or newer. The 8.3 branch gets security fixes for several more years, and most popular plugins have already been tested on it. There's no point moving to 8.2 now: it goes out of support on December 31, 2026.
When you're done, put the line define( 'WP_DEBUG', false ); back in wp-config.php and delete wp-content/debug.log. That file can be opened from a browser, and it shows server paths.
When it's better to call a developer
You can handle it yourself if a single plugin is to blame and a fresh version of it exists. Call us if:
- the error is in a theme that was once built to order and has no updates;
- the site doesn't open even with all plugins disabled;
- it's a store, and every hour of downtime is lost orders;
- you aren't sure the backup can actually be restored.
We check the site for free and tell you what exactly broke. Fixing a critical error is $25 per hour, and one or two hours is usually enough. A turnkey PHP update with a backup, a test on a copy and the switch-over is $50. Details are on the urgent PHP update page. If you want such things never to come as a surprise, look at website support.
If the theme and plugins are so old that patching them costs more than rebuilding, see turnkey WordPress website development.