WordPress critical error: what it means and how to fix it

What the WordPress critical error means

A WordPress critical error is not a diagnosis by itself. It is the public error screen WordPress shows when PHP stops execution because of a fatal error. On current WordPress versions, Recovery Mode may also send the site administrator an email identifying the component that failed and giving a special login link.

The useful evidence is the underlying PHP message. It may name a file inside wp-content/plugins or a theme directory, report an undefined function or class, show an exhausted memory limit, or point to code that is not compatible with the PHP version running on the server. If the site failed immediately after an update, deployment or PHP upgrade, start with that change rather than making several changes at once.

Common causes of a critical error in WordPress

The most common cause is a plugin or theme executing PHP that cannot run successfully. That can happen after an update introduces a bug, two extensions conflict, custom code calls a function that is no longer available, or an older extension is run on a newer PHP 8.x version. A partially completed update can also leave files out of sync.

Resource failures are another common trigger. A plugin performing a large import, backup, image operation or database task can hit the PHP memory limit or execution time. Less often, damaged files, incorrect permissions or a server level PHP configuration change can expose a fault that was previously hidden.

If the error email or log names a specific path, treat that path as evidence. A file under wp-content/plugins/plugin-name/ usually points to that plugin, while a path under the active theme usually points to the theme or its custom code.

How to fix a WordPress critical error safely

Before editing files or the database, take a full backup of both website files and the database. Then work through the following steps in order.

1. Check the WordPress administrator email for a Recovery Mode message. If it identifies a plugin or theme, use the Recovery Mode link and deactivate the named component.
2. If the dashboard is unavailable, use your host file manager or SFTP. Rename only the suspected plugin folder inside wp-content/plugins. If you do not know which plugin is responsible, WordPress documentation describes temporarily renaming the plugins folder to disable plugins, then restoring the folder name and reactivating plugins one at a time.
3. If the problem started after a theme change, switch to a current default WordPress theme from the dashboard or with help from your host.
4. For diagnosis, log errors instead of displaying them to visitors. In wp-config.php, use:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

Reload the failing page once, then inspect wp-content/debug.log. Turn debugging off again after diagnosis. Do not leave a public debug log exposed on a live site.

When to stop troubleshooting and get help

Stop if the error points into unfamiliar custom PHP, repeats after the obvious plugin or theme rollback, affects checkout or other business critical functions, or you cannot make a verified backup. Also stop if the log shows repeated fatal errors across several components, because the first visible failure may not be the root cause.

Web Support Services offers an Emergency Fix for £249 per incident, with a response within 2 working hours. If you want ongoing updates, backups and monitoring, care plans start from £59 a month.