WordPress not working after PHP upgrade usually means a plugin, theme or missing PHP extension does not work with the new version. You will get the site back online with a quick rollback, find the real error in a log file, and fix the cause so the upgrade can stick.
Typical symptoms are a white screen, a “critical error” message, a broken dashboard or missing thumbnails. Most of them trace back to an error PHP writes to a log, so we get the site online first and then read that log.
Bring the site back online first with a PHP rollback
The fastest recovery is usually to switch PHP back to the previous version. Open the PHP version tool in your hosting control panel (in cPanel it is called MultiPHP Manager), choose the previous version for the domain, save, then reload the front end and wp-admin. A rollback changes only the PHP version and does not touch your content, but take a backup first anyway.
Treat the rollback as temporary. If the older version no longer gets security fixes, you still need to fix the underlying problem. For related server-side failures, see our guide to fixing WordPress Error 500.
Check for a .maintenance file
If the site shows “briefly unavailable for scheduled maintenance”, a leftover .maintenance file is sitting in the WordPress root. Turn on “show hidden files” in your file manager, because dotfiles are hidden by default. Delete the file and reload.
Use the Recovery Mode email link
After a fatal error, WordPress may email a Recovery Mode link to the site’s admin address. Open it, log in, and WordPress will show which plugin or theme caused the error and let you deactivate it.

Turn on debug logging and read the real error
Open wp-config.php and add these lines above the comment that says “That’s all, stop editing!”:
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);
WordPress now writes errors to wp-content/debug.log. Keep WP_DEBUG_DISPLAY set to false on a live site so visitors never see raw errors. Reload the broken page, then open the log.
Read the message, file path and line number
A typical entry looks like this: PHP Fatal error: Uncaught Error: Call to undefined function some_old_function() in /wp-content/plugins/example-plugin/main.php on line 214. Read it in three parts: the message, the path after “in”, and the number after “on line”. The path tells you who owns the problem.
| Path contains | Likely owner |
|---|---|
| wp-content/plugins/name | That plugin |
| wp-content/themes/name | That theme |
| wp-includes or wp-admin | Core, but check the stack trace |
Follow the stack trace to the failing plugin or theme
When the path points to core, scroll through the “Stack trace” lines that follow. The first line that mentions plugins or themes is usually the real source, because core was only running code that plugin or theme handed to it.
Check the hosting error log as well
Some fatal errors never reach debug.log, for example when they happen before WordPress loads. Check the PHP error log in your hosting panel too. When you are finished, set WP_DEBUG back to false (or remove the lines) and delete debug.log.

Isolate the cause by disabling plugins and switching themes
Renaming folders can break the site for visitors while you test. Do this on staging or in a quiet window.
Rename the plugins folder to test
- In your file manager or over SFTP, rename
wp-content/pluginstoplugins_old. - Reload the site and wp-admin.
- If it works, rename the folder back to
plugins. - Go to Plugins > Installed Plugins and reactivate them one at a time, reloading the site after each one, until the error returns. The last plugin you activated is the culprit.
Once you have found the culprit, update it, replace it, or contact its author. If the broken part is checkout, our notes on WooCommerce payment troubleshooting cover the next steps.
Test the theme with a folder rename
Rename the active theme’s folder inside wp-content/themes, for example mytheme to mytheme_old. WordPress falls back to a default theme if one is installed. If the error disappears, the theme is the cause. Rename the folder back afterwards and ask the theme developer for a version that supports your PHP version.
When wp-admin is broken but the front end works
This split often points to an admin-only plugin or to a hook that runs only in the dashboard. Search debug.log first for entries that mention wp-admin paths or admin-ajax.php, then test the plugins named in those lines.
Check PHP extensions and memory limits
A PHP upgrade can drop or change loaded extensions, because each PHP version is configured separately on many hosts. Open Tools > Site Health > Info to see the PHP version in use, and check the Media Handling section to see whether GD or Imagick is available. Then confirm that GD, Imagick, mysqli and mbstring are loaded in the new version.
Confirm the extensions the site needs
Your hosting panel usually has an extension list for each PHP version. If it does not, upload a temporary file named check-ext.php to the WordPress root:
<?php
foreach (['gd', 'imagick', 'mysqli', 'mbstring'] as $ext) {
echo $ext . ': ' . (extension_loaded($ext) ? 'loaded' : 'MISSING') . '<br>';
}
Open it in your browser, then delete it straight away.
Fix thumbnails and uploads
If GD and Imagick are both missing, WordPress cannot resize images, so thumbnails and uploads fail. Enable at least one of them for the new PHP version in your host’s panel, or ask your host to do it.
Raise the memory limit correctly
For “allowed memory size exhausted” errors, add this to wp-config.php above the stop-editing line, or use your host’s PHP memory setting if it has one:
define('WP_MEMORY_LIMIT', '256M');
A higher limit only buys headroom. If the error returns, look in debug.log for the plugin path named in the message and test that plugin first.
Audit plugins and themes and plan a supported PHP version
Do this audit before the next upgrade, not after. Core is rarely the problem, because each WordPress release documents which PHP versions it supports. Check that list on WordPress.org before choosing a PHP version, then audit the plugins and themes, which are the usual cause.
Check each plugin’s declared PHP requirement
Open each plugin’s main file or readme.txt and look for the Requires PHP field. Also check when the plugin was last updated. If it is abandoned,



