WordPress critical error recovery mode is a built-in emergency feature — introduced in WordPress 5.2 (released May 2019) — that lets a site administrator log into the dashboard and deactivate a faulty plugin or theme even when the site's frontend is broken. If you're currently staring at the message "There has been a critical error on this website," your site isn't lost, and in most cases you can fix it without touching a single line of code.
Knowing how to recover your site quickly is part of the real cost of running a WordPress site in South Africa — downtime costs money, and the fix is usually faster than most owners expect.
The error almost always has one of four causes: a newly installed or updated plugin that conflicts with your WordPress version or PHP version, a theme update that broke something, a corrupted core file, or your server running out of PHP memory. The fix route depends on what you can still access — and that's exactly what this guide maps out.
Quick Answer
WordPress critical error recovery mode is an automatic safe-access feature that activates when WordPress detects a fatal PHP error. WordPress sends an email to the site admin with a unique recovery link — click it, log in, and deactivate the broken plugin or theme from within the dashboard. If the email doesn't arrive, the officially documented fallback is to rename the plugins folder via your hosting file manager (cPanel on most South African hosts) — no email link needed. Either way, your content and database are untouched.
Jump to a section
Is a broken site costing you customers right now?
Send us a message and we'll assess the issue and let you know what's causing it — no obligation.
Get a free site assessmentWhat Triggers a WordPress Critical Error?
A WordPress critical error occurs when a fatal PHP error prevents WordPress from completing a page load — the site doesn't just look broken, it fails at the server level before the page can render. The four most common causes are:
| Cause | How to recognise it | Fix route |
|---|---|---|
| Plugin conflict or bad update | Error followed a plugin install or update | Deactivate via recovery mode or file manager |
| Theme conflict or bad update | Error followed a theme switch or update | Revert to default theme via file manager |
| PHP version mismatch | Error after hosting company upgraded PHP on the server | Contact host to roll back PHP version temporarily |
| PHP memory exhaustion | Error appears intermittently under load | Increase WP_MEMORY_LIMIT in wp-config.php |
In every case, your WordPress database and all your content are safe — a critical error is a code failure, not a data loss event. The right approach to any wordpress critical error fix starts with identifying which of these four causes applies before touching any files.
Key point: A WordPress critical error is almost always caused by a plugin, theme, or PHP configuration change — not by your content or database. Your posts, pages, products, and customer records are intact. The job is identifying and removing the broken code.
How WordPress Critical Error Recovery Mode Works
WordPress critical error recovery mode is a cookie-based safe-access mechanism: when WordPress detects a fatal PHP error, it pauses the problematic plugin or theme only for the administrator who clicked the recovery link — your regular site visitors are unaffected in terms of data, though they still see the error message until the underlying problem is fixed.
Here's the full sequence from error to resolution:
- WordPress detects a fatal PHP error during a regular page load.
- The frontend displays: "There has been a critical error on this website."
- WordPress emails the site administrator (to the address stored in Settings → General) with the subject "Your Site is Experiencing a Technical Issue."
- The email names the file or plugin that caused the error and includes a unique recovery link.
- Clicking that link places a session cookie on your browser — you're now in recovery mode.
- The faulty component is paused for your session only; you land in the dashboard with an admin notice identifying the problem.
- You deactivate the broken plugin or revert the theme, then click "Exit Recovery Mode" in the toolbar.
- The site resumes normal operation.
This is the official WordPress recovery mode mechanism, introduced in WordPress 5.2 to replace the old "white screen of death" that previously required direct server or developer access to fix. The feature is built specifically around wordpress fatal error recovery — giving non-technical site owners a self-service path that doesn't require FTP access or PHP knowledge for the most common cases.
One important limitation: the recovery email is sent when WordPress first detects the error. If the email is rate-limited or doesn't arrive (more on that below), you have two fallback routes.
Path 1: Using the Recovery Mode Email
The recovery mode email is the fastest and cleanest route — most users complete the fix without touching a single server file.
- Check your admin email inbox — look for "Your Site is Experiencing a Technical Issue." Also check your spam folder; recovery emails sent directly from the web server often get filtered if your host's IP isn't fully trusted.
- Check that the right email address is listed in your WordPress dashboard under Settings → General → Email Address. If a previous developer set up the site, the admin email may be an address you don't have access to.
- Click the recovery link in the email. You'll reach a login page with a notice that says "Recovery Mode Initialized."
- Log in with your WordPress admin credentials.
- Read the admin notice — it will identify which plugin or theme caused the fatal error, usually with the filename and error message.
- Go to Plugins → Installed Plugins and deactivate the identified plugin. If the error points to a theme, go to Appearance → Themes and switch to a default WordPress theme (Twenty Twenty-Four or Twenty Twenty-Five).
- Click "Exit Recovery Mode" in the admin toolbar, then reload your site to confirm it's working.
- Address the root cause — check whether an update is available for the plugin or theme, or contact the plugin developer about the incompatibility.
Good practice: Before reactivating the plugin or reinstalling the theme, confirm which version broke the site and whether an updated version is available. Many plugin-related critical errors are resolved within days of the developer releasing a compatibility patch.
When the Recovery Mode Email Doesn't Arrive
When the recovery mode email doesn't arrive, your most reliable next step is to access your site files directly through your hosting control panel — no email link is needed to rename the plugins folder and restore access. The official WordPress documentation points straight to the file manager route when the email fails; the steps are in Path 3 below.
The three most common reasons the email doesn't arrive: the fatal error occurred before your SMTP or email plugin loaded, so WordPress fell back to direct server mail that many providers flag as spam; the admin email stored in Settings → General is outdated; or the email landed in spam. Check your spam folder and confirm the correct email address before moving on.
If checking spam and confirming the email address don't resolve it, go straight to Path 3 — the file manager route works regardless of email delivery and takes only a few minutes with cPanel access.
Preventing future email delivery failures
WordPress sends outgoing emails directly from your web server by default — a method that many email providers reject as spam. Installing an SMTP plugin (WP Mail SMTP or Post SMTP) routes your WordPress emails through a trusted mail service (Gmail, Outlook, or a transactional provider like SendGrid or Mailgun) and prevents recovery emails from going missing. This is standard practice on well-maintained SA WordPress sites.
Locked Out Completely — The File Manager Route
If neither the recovery email nor the manual URL works, you access your site files directly through your hosting control panel's file manager or via FTP. Most South African hosting providers — including Xneelo (formerly Hetzner), HOSTAFRICA, and Domains.co.za — include cPanel with a built-in File Manager, so you won't need to download a separate FTP client.
Disabling all plugins via file manager
- Log in to your hosting control panel (cPanel or DirectAdmin).
- Open File Manager and navigate to
public_html/wp-content/(or the folder where your WordPress site is installed). - Right-click the
pluginsfolder and rename it toplugins-disabled. This deactivates every plugin immediately — WordPress can't find the folder, so it loads without them. - Reload your site. If the critical error clears, one of the plugins was the cause.
- Rename the folder back to
plugins, then open it and reactivate plugins one by one — returning to your site after each — until the error reappears. The last plugin you activated is the culprit.
Switching to a default theme via file manager
If disabling plugins doesn't clear the error, the problem is likely in your theme:
- In File Manager, navigate to
public_html/wp-content/themes/. - Rename your active theme folder (e.g.
my-theme→my-theme-disabled). - WordPress will automatically fall back to the most recently installed default theme (Twenty Twenty-Four or Twenty Twenty-Five).
- Reload your site to confirm the error is resolved.
File manager rule: Rename folders — don't delete them. Renaming is reversible in seconds; deletion permanently removes your plugin or theme files. Always rename, never delete, when troubleshooting.
Increasing PHP memory as a fix
If the error appears intermittently or under load, PHP memory exhaustion may be the cause. Edit wp-config.php (in the root WordPress folder) and add this line before the /* That's all, stop editing! */ comment:
define('WP_MEMORY_LIMIT', '256M');Note that this setting can only raise memory up to your server's PHP limit set in php.ini — if 256M doesn't take effect, contact your hosting provider to raise the server-level limit.
Finding the Root Cause with Debug Mode
Once you've restored access, enable WordPress debug logging to capture the exact error message — particularly useful when a critical error on a WordPress site recurs or when the cause isn't obvious from the recovery mode notice.
Edit wp-config.php and add these three lines before the stop-editing comment:
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);WordPress will write all PHP errors to wp-content/debug.log. You can read this file via File Manager. The log entries show the exact filename, line number, and error type — which makes it straightforward to identify whether the problem is in a specific plugin, the theme's functions.php, or a custom code snippet.
Important: Disable debug mode once you've identified the issue. Leaving WP_DEBUG active on a live site can expose error details to visitors if display settings aren't configured correctly.
For ongoing website uptime monitoring, consider a tool that alerts you the moment your site goes down — so you learn about critical errors before your customers do. Pair this with a solid website maintenance routine that keeps plugins and themes updated on a schedule rather than reactively.
Not sure whether your site is properly maintained?
Share your WordPress setup with us and we'll identify which plugins, theme versions, or hosting configurations put you at risk of this error recurring.
Get a maintenance assessmentWhy South African Businesses Choose Growth Pulse Media
Growth Pulse Media is a Johannesburg-based digital agency built by Dirk van Greuning, who built and scaled a large South African ecommerce business before founding the agency. That background matters when a client's WordPress site goes down mid-campaign: the instinct is to fix the revenue problem, not just the technical one.
Our web design work includes WordPress sites built with maintainability as a core requirement — that means a minimal, curated plugin stack, tested PHP compatibility, and hosting configurations that don't accumulate technical debt. We don't hand over a site and leave you to discover what breaks when the first plugin update rolls through.
We work with a limited client load so every site gets senior attention, not junior account management. All work is executed in-house — no white-labelling, no offshore handoffs.
Who This Is NOT For
Not for sites with no backup. Recovery mode restores access so you can deactivate the broken component — but if a previous fix attempt accidentally deleted a plugin or theme folder, you need a backup to restore it. If your current host doesn't provide automated daily backups, address that before your next update cycle.
Not for errors caused by custom code in functions.php. If a developer added custom code directly to your theme's functions.php and that code has a syntax error, recovery mode will identify the theme as the problem — but deactivating the theme removes your entire site design. In this case, use the debug log to identify the specific line, correct the code via file manager, and restore the theme.
Not for multisite networks experiencing a network-wide error. WordPress recovery mode has limitations on multisite installations — a network-level fatal error may not trigger the recovery email to sub-site administrators. In this case, the network admin needs to troubleshoot at the network level, typically via FTP access to the main installation.
Frequently Asked Questions
What does "There has been a critical error on this website" mean in WordPress?
It means WordPress encountered a fatal PHP error that prevented the page from loading completely. The message is displayed to frontend visitors while WordPress simultaneously sends a recovery email to the site admin. The error is almost always caused by an incompatible plugin, a broken theme, or a PHP configuration issue — not by your content or database.
How do I fix a WordPress critical error if the recovery mode email doesn't arrive?
Use the file manager route: log in to your hosting control panel (cPanel on most South African hosts), navigate to wp-content, and rename the plugins folder to disable all plugins at once. WordPress loads without them, clearing the error. You can then identify the culprit by reactivating plugins one by one — the plugin that brings the error back is the cause. Check your spam folder and confirm the admin email address in Settings → General is current before assuming the email was lost.
Why didn't I receive the WordPress recovery mode email?
The most common reasons are: the fatal error occurred before your SMTP or email plugin loaded, so WordPress fell back to direct server mail which often gets spam-filtered; the admin email address stored in Settings → General is outdated; or the email arrived in your spam folder. Installing a dedicated SMTP plugin (WP Mail SMTP or Post SMTP) prevents this from recurring by routing WordPress emails through a trusted mail service.
Will recovery mode fix my site permanently?
Recovery mode gives you dashboard access so you can deactivate the broken plugin or revert the theme — that stops the immediate error. It's a temporary measure that restores the site while you address the underlying cause, which usually means updating the plugin to a compatible version, contacting the developer about the incompatibility, or removing the plugin and finding an alternative.
How do I stop WordPress critical errors from happening again?
Three practices reduce recurrence significantly: keep WordPress core, plugins, and themes updated on a regular schedule (not reactively); test updates on a staging environment before applying them to your live site; and configure an SMTP plugin so recovery emails reliably reach you when something does go wrong. For higher-risk sites, automated daily backups mean any failed update can be rolled back within minutes.
WordPress problems costing you time and customers?
Growth Pulse Media builds and maintains WordPress sites for South African businesses — with a curated plugin stack, tested update workflows, and a setup that doesn't break under routine maintenance. No obligation — we'll get back to you within 24 hours.
Talk to us about your site

