How to Fix 'There Has Been a Critical Error on This Website'

You log into your WordPress admin dashboard on a busy afternoon. You see a notice saying: "3 Plugins Have Available Updates".

You click "Update".

Suddenly, your browser refreshes and presents a blank white screen with terrifying bold text:

"There has been a critical error on this website. Please check your site admin email inbox for instructions."

You try navigating to your homepage — broken. You try navigating to

/wp-admin/

Your website is offline, your online store has stopped taking orders, and you cannot even log in to deactivate the plugin that caused the crash.

Don't panic. This is the modern version of the WordPress "White Screen of Death (WSOD)". It almost always boils down to a PHP fatal error or memory limit exhaustion caused by an incompatible plugin or theme update.

Here is the exact step-by-step emergency workflow to recover your website in under 5 minutes.

What Causes the WordPress Critical Error?

When WordPress displays this message, PHP has encountered an unhandled fatal error and stopped execution to prevent data corruption.

The three most common triggers include:

1. PHP Version Incompatibility: A newly updated plugin requires PHP 8.2 or 8.3, but your South African host is still running PHP 7.4.
2. Plugin Conflict (Fatal Function Redeclaration): Two plugins trying to use the same library or declare the same helper function name.
3. PHP Memory Limit Exhaustion: An update pushed your site over your server's 128MB or 256MB PHP memory threshold.

How to Recover Your Crashed WordPress Website

Follow these steps in order. You do not need access to

wp-admin

Step 1: Check Your Admin Email for the WordPress Recovery Link

WordPress includes an automated crash handler. When a critical error occurs:

• Check the administrative email address associated with your WordPress site.
• Look for an email with the subject line:

  [Your Site] Your Site is Experiencing a Technical Issue

  .
• The email will contain the exact name of the faulty plugin and a special Recovery Mode URL that allows you to log into

  wp-admin

  safely to deactivate the rogue plugin.

Step 2: Disable the Problematic Plugin via cPanel / File Manager / FTP

If you did not receive the recovery email:

1. Log into your hosting control panel (cPanel, DirectAdmin, konsoleH, or SFTP).
2. Open File Manager and navigate to your website root:

   public_html/wp-content/plugins/

   (or

   www/wp-content/plugins/

   ).
3. Locate the folder of the plugin you just updated (e.g.

   woocommerce-gateway-plugin

   ).
4. Rename the folder by adding

   -disabled

   to the end (e.g.

   woocommerce-gateway-plugin-disabled

   ).
5. Refresh your website in your browser. WordPress will automatically deactivate the missing plugin, and your site will immediately come back online.

Step 3: Enable WordPress Debug Mode to See the Exact Line of Error

If renaming a single plugin doesn't restore the site, turn on WordPress error logging to see the exact file and line number causing the crash:

1. In File Manager, open your

   wp-config.php

   file in your root folder.
2. Find the line

   define( 'WP_DEBUG', false );

   and change it to:

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

3. Reload your broken website once.
4. Open the newly generated log file at

   wp-content/debug.log

   . The very last line will display the exact plugin name, file path, and error code.

Step 4: Increase Your PHP Memory Limit

If your

debug.log

Allowed memory size of X bytes exhausted

wp-config.php

define( 'WP_MEMORY_LIMIT', '512M' );

How to Prevent Future Update Disasters

To ensure your live business never goes down during updates again:

• Never update plugins during peak business hours (Fridays at 4 PM or right before a sale).
• Always run automated backups before running major core or WooCommerce updates.
• Test major updates on an isolated staging subdomain first.

Need Emergency Help Getting Your Site Back Online?

If your site is stuck on a critical error, checkout is broken, or database corruption is preventing you from restoring access, don't waste hours guessing.

Message Darren on WhatsApp for same-day emergency WordPress recovery. I'll identify the offending code, restore your site to full health, and ensure your backups are working properly.