How to Fix WordPress Critical Error (This Site Is Experiencing a Technical Issue)

by

What Is the “Critical Error” in WordPress?

Since version 5.2, WordPress introduced a feature called “Fatal Error Protection.” Instead of showing a blank white screen (the “White Screen of Death”), WordPress now displays a formal error message: “There has been a critical error on this website. Please check your site admin email inbox for instructions.”

This error is essentially a “crash report.” It means a script on your site has failed so completely that WordPress had to stop the entire page from loading to prevent further damage.

Common Causes of the WordPress Critical Error

  • PHP Fatal Errors: A plugin or theme has a syntax error or a conflict that crashes the PHP engine.
  • Memory Exhaustion: Your site ran out of RAM while trying to process a heavy task.
  • Plugin/Theme Conflicts: Two pieces of software are trying to use the same function name or resource.
  • Corrupted Files: A core WordPress file was modified or deleted incorrectly.
  • Incompatible PHP Version: You updated a plugin that requires PHP 8.1, but your server is on PHP 7.4.

Step-by-Step Fixes for the Critical Error

1. Check Your Admin Email (The “Recovery Mode” Fix)

When a critical error occurs, WordPress automatically sends an email to the site’s administrator. This is the “safe way” to fix your site.

  1. Check the email account associated with your WordPress site.
  2. Look for an email with the subject: “Your Site is Experiencing a Technical Issue.”
  3. Pro Tip: If you don’t see it, check your Spam or “Promotions” folder. Sometimes these automated emails are flagged as bulk mail.
  4. Inside, you will find a Recovery Mode link.
  5. Click the link. This allows you to log in to the backend even if the front end is crashing. WordPress will pinpoint the exact plugin or theme causing the crash.

2. Enable WordPress Debug Mode (Finding the invisible error)

If you didn’t receive an email, you need to “force” WordPress to stop being polite and start being specific about its problems.

  1. Connect to your site via FTP or cPanel File Manager.
  2. Open the wp-config.php file.
  3. Find the line that says define( 'WP_DEBUG', false );.
  4. Change it to true:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false ); // Log errors privately instead of showing them to visitors
  1. Save the file and refresh your website. Then, go to /wp-content/ and look for a new file called debug.log. It will show you the exact file path and line number of the fatal error.

Why “Critical Error” is Actually a Good Thing

Before WordPress 5.2, a fatal error meant your site simply disappeared into a “White Screen of Death,” leaving you completely in the dark. The “Critical Error” message and Recovery Mode are safety nets. They prevent your site from silently failing and offer a guided path to recovery that doesn’t always require editing code.

3. Deactivate the Offending Plugin or Theme

Once Debug Mode tells you which file is broken (e.g., /wp-content/plugins/slash-editor/...), you can fix it.

  1. Navigate to the folder mentioned in the error message.
  2. Rename that folder (e.g., slash-editor-old).
  3. Refresh your site. It should now load normally.

4. Increase PHP Memory Limit

If the error message mentions “Allowed memory size… exhausted,” your server needs more RAM.

  1. In wp-config.php, add this line:
define('WP_MEMORY_LIMIT', '256M');
  1. This gives the crashing script more space to run, which often resolves the critical error immediately.

How to Verify the Fix Worked

  • Exit Recovery Mode: If you used the email link, make sure to click “Exit Recovery Mode” in the top admin bar to ensure the site works for regular visitors.
  • Turn Off Debugging: Once the site is fixed, always change WP_DEBUG back to false. Leaving it on can expose security details about your server to visitors.
  • Check Dashboard: Ensure you can navigate to Plugins and Themes without the error reappearing.

Leave a Comment