Skip to content
webfixed

Guides / WordPress

There has been a critical error on this website: how to fix it

By Michael Broadbridge. Last checked 14 November 2026 on WordPress 7.1.

Short answer

"There has been a critical error on this website" means PHP code has crashed, usually in a plugin, sometimes in the theme or after a PHP version change. Look for an email from WordPress at the site’s administration email address and use its recovery mode link. If no email arrives, rename the plugin’s folder using your host’s file manager.

Symptoms

You may see one of these messages:

There has been a critical error on this website.

There has been a critical error on this website. Please check your site admin email inbox for instructions. If you continue to have problems, please try the support forums.

There has been a critical error on this website, putting it in recovery mode. Please check the Themes and Plugins screens for more details. If you just installed or updated a theme or plugin, check the relevant page for that first.

  • The site shows "There has been a critical error on this website." instead of your pages.
  • The dashboard or login page shows a longer version that asks you to check your site admin email inbox for instructions.
  • The error appeared straight after a plugin, theme or WordPress update, or after your host changed the PHP version.
  • An email with the subject "Your Site is Experiencing a Technical Issue", after the site name in square brackets, has arrived at the site’s administration email address.

Causes, most likely first

  1. A plugin update

    A plugin update that contains a bug or clashes with another plugin is the most common cause.

  2. A PHP version change

    A plugin or theme that does not work with the PHP version your host runs, often after the host has moved the site to a newer PHP release.

  3. A theme update or theme code

    A theme update, or custom code added to the theme’s functions.php file.

How to fix it

Use the recovery mode email first

When WordPress catches a fatal error in a plugin or theme, it emails the Administration Email Address set under Settings, then General. The subject is the site name in square brackets followed by "Your Site is Experiencing a Technical Issue". The email names the plugin or theme, lists the file and line under Error Details, and contains a recovery mode link. WordPress sends this email at most once a day, and the link expires after the same period. Your content and database are not affected.

  1. Search the inbox and the spam folder of the administration email address for a message from WordPress.
  2. Click the recovery mode link in the email and log in with your normal username and password.
  3. WordPress opens the dashboard with the faulty plugin or theme paused, and shows a notice naming it.
  4. Click Deactivate on the plugin marked as paused. The Paused filter at the top of the list shows it.Menu: Plugins > Installed Plugins
  5. If the theme is named instead, activate a different theme.Menu: Appearance > Themes
  6. Click Exit Recovery Mode in the bar at the top of the screen, then open the site in a private browser window to check it loads.

Leaving recovery mode before you have deactivated the faulty plugin or theme brings the error back for every visitor.

If there is no email, switch plugins off through the file manager

Many sites cannot send email reliably, so the recovery message never arrives. You can switch plugins off without the dashboard by renaming their folders. Use the file manager in your hosting control panel, or an SFTP program such as FileZilla with the login details from your host.

  1. Open the folder that contains your site, often called public_html, then open wp-content, then plugins.
  2. If you know which plugin was updated or installed last, rename its folder by adding -off to the end of the name. This deactivates that one plugin.
  3. Reload your site. If it is back, you have found the cause.
  4. If you do not know which plugin is at fault, go up one level and rename the whole plugins folder to plugins-off. This deactivates every plugin at once.
  5. If the site now loads, rename the folder back to plugins. Every plugin stays deactivated. Log in and reactivate them one at a time, reloading the site after each one until the error returns.Menu: Plugins > Installed Plugins

Renaming a folder does not delete the plugin’s settings, which are stored in the database. Do not delete plugin folders unless you are sure you no longer need the plugin.

Check the theme and the PHP version

  1. If the error remains with every plugin switched off, go to wp-content, then themes, and rename the folder of your active theme.
  2. WordPress falls back to a default theme such as Twenty Twenty-Five, provided one is still installed. Your site will look different while you test.
  3. If the site loads, the theme is the cause. Your theme settings return when you rename the folder back and reactivate the theme.
  4. If you can log in, check which PHP version the site runs. Open the Info tab and look under Server.Menu: Tools > Site Health
  5. If your host recently moved the site to a newer PHP version, switch back one version in the PHP settings of your hosting control panel and reload the site.

If going back a PHP version fixes it, an out of date plugin or theme is the real cause and needs updating or replacing. WordPress recommends PHP 8.3 or newer, and older versions no longer receive security fixes.

Turn on the debug log to see the exact error

WordPress can write the full error to a log file, which shows the exact file and line that failed. Download a copy of wp-config.php before editing it, because a typing mistake in this file will take the site offline.

  1. Open wp-config.php, which sits in the main folder of your site, in the file manager’s editor.
  2. Find the line define( 'WP_DEBUG', false ); and change false to true. If there is no such line, add it above the line that begins "That’s all, stop editing".
  3. Directly underneath, add these two lines: define( 'WP_DEBUG_LOG', true ); and define( 'WP_DEBUG_DISPLAY', false );
  4. Save the file and reload the broken page once.
  5. Open wp-content and look for a file called debug.log. The most recent lines marked "PHP Fatal error" include a file path, and the folder name in that path shows which plugin or theme is responsible.
  6. When you have finished, set WP_DEBUG back to false and delete debug.log. The log sits in a public folder, and WordPress warns that a log in a public location is a security risk.

Restore a backup if nothing else works

Most hosts keep daily backups that you can restore from the control panel, and backup plugins such as UpdraftPlus keep their own copies. Restore the most recent backup from before the error started. Restoring the files only, and leaving the database alone, is often enough after a bad update and avoids losing anything recent.

A full restore replaces the database as well, so any orders, form entries, comments or edits made after the backup date will be lost. On a shop, export recent orders first if you can reach them.

If that didn’t work

  1. The site has run out of PHP memory

    Each page is allowed a set amount of server memory. If the debug log mentions memory, the limit needs raising in your hosting control panel or by your host.

  2. A failed or half-finished update

    An interrupted update can leave files missing. Restoring the files from a backup taken before the update puts them back.

  3. Unrecognised files

    If the debug log names files you do not recognise, or the error appeared with no updates at all, scan the site for malware.

When to get help

Stop if the recovery email never arrives and you are not comfortable using SFTP or the file manager, if the debug log points at WordPress core files or the database, or if the error comes back every time you reactivate a plugin the site depends on. Get help straight away if this is a shop that is losing orders while it is down.

What a developer would check

  • The PHP fatal error in the debug log or the host’s error log, and the file and line it names.
  • Whether each plugin and the theme support the PHP version the host is running.
  • Plugin conflicts, by reactivating plugins one at a time on a staging copy.
  • Whether the WordPress core files are complete and unmodified.

Describe the problem in your own words and WebFixed gives you an instant fixed quote. Nothing is charged until you accept it.

Related questions

Will I lose my content because of the critical error?
No. The error stops pages from being displayed, but your posts, pages, products and images remain in the database and the uploads folder. They reappear once the faulty plugin, theme or setting is dealt with.
Why did I not receive the recovery mode email?
It goes to the Administration Email Address under Settings, then General, which is often an old address or the address of whoever built the site. WordPress also sends it no more than once a day, and many hosts send WordPress email unreliably, so it may have been blocked or marked as spam.
Does the critical error mean my site has been hacked?
Usually not. It is nearly always a code fault after an update or a PHP version change. If the debug log names files you do not recognise, or the error appeared with no updates at all, scan the site for malware.

Written by Michael Broadbridge, Founder of Webgro. First published 21 September 2026. Last checked 14 November 2026 on WordPress 7.1.