"There Has Been a Critical Error on This Website": What It Means and How to Fix It
“There has been a critical error on this website” is the message WordPress shows when a fatal PHP error stops the site from loading. It is usually caused by a plugin, a theme or a PHP version problem, and it can almost always be fixed once the exact cause is found in the error details.
What the critical error message means
WordPress runs on PHP. When PHP hits an error it cannot recover from, such as a missing function or incompatible code, it stops. Since WordPress 5.2, instead of leaving a blank page, WordPress catches many of these fatal errors and displays a friendly message. The words are generic, but the cause is specific and recorded behind the scenes.
The most common causes
- A plugin update that is not compatible with your theme, WordPress version or PHP version
- A theme update or a change to custom code in the theme’s functions file
- A PHP version upgrade at the host that older plugins or themes cannot handle
- An interrupted update that left files incomplete
- A plugin that needs another plugin which has been deactivated or removed
- Running out of PHP memory during a heavy operation
Not sure what is going on with your website?
Tell us what you are seeing and we will outline the next step before any chargeable work.
Check your email for the recovery link
WordPress usually sends a message to the site administrator email address when it detects a fatal error. It names the plugin or theme responsible and includes a special recovery mode link. That link lets an administrator log in and deactivate the failing component without touching any files. If you cannot find it, check spam folders and any old administrator address.
A safe way to approach the fix
| Step | Why it matters |
|---|---|
| 1. Note what changed | Most critical errors follow a specific update or edit |
| 2. Secure a backup | Protects content and orders before any change |
| 3. Read the error details | The log names the file and plugin at fault |
| 4. Isolate the cause | Disable only the suspected component, ideally on a copy |
| 5. Fix, not just hide | Update, replace or reconfigure so the fault does not return |
| 6. Test key pages | Check forms, login and checkout still work |
Why switching everything off is risky
A common piece of advice is to rename the plugins folder so that every plugin is deactivated. That works as a diagnostic, but on a live website it can break layouts, reset settings and take forms or checkout offline while you test. It also teaches you nothing about which plugin was the problem. Targeted isolation with a recovery point is safer.
Reading the error details yourself
The generic message hides a specific record. If you have hosting access, your control panel usually offers an error log. The most recent lines often include a path such as wp-content/plugins/some-plugin/file.php and a short description like “Call to undefined function”. That path names the plugin or theme at fault, and the description hints at why. Even if you do not fix it yourself, copying those lines into your request for help saves time and cost.
WordPress can also display the underlying error on screen when debugging is switched on. This should only ever be done briefly and on a copy of the site, because error details can reveal file paths and other information that visitors should not see.
What a good fix looks like
A good fix does three things. It restores the website. It addresses the cause, for example by updating, replacing or reconfiguring the failing component. And it leaves you with an explanation in plain English, so you know what happened and how to avoid it. Be wary of fixes that simply hide the error or delete the component without checking what depends on it.
- The website works again and key pages have been tested
- The failing plugin, theme or setting has been identified
- You know whether anything needs replacing, updating or monitoring
- A recent backup exists in case the fault returns
How to reduce the chance of seeing it again
Critical errors are most often triggered by changes. Apply updates one at a time, check the website after each, and avoid installing plugins you do not need. Keep PHP versions in step with what your plugins support, and test major WordPress or PHP upgrades on a staging copy first. If you would rather not manage that yourself, WordPress maintenance bundles managed updates, backups and monitoring, so the next update is tested before it reaches your customers.
What the recovery mode link actually does
The recovery mode link in the WordPress email opens a special session in which WordPress pauses the failing plugin or theme for you alone, so you can log in and see the dashboard while visitors still see the error. Inside that session you can deactivate or update the problem component, then exit recovery mode. It is a clean, reversible step that avoids editing files by hand. If the link has expired, WordPress can usually send a fresh one when you trigger the error again, though a developer with hosting access can do the same without the email.
How long a fix should take and what it should cost
Many critical errors are quick to fix once the cause is known, because the error log names the file at fault. Cost and time rise when the cause is a plugin that has been abandoned, when several components are involved, when custom code is at fault or when there is no backup to protect while you work. A sensible provider assesses first, explains what they found, and gives you a quote before chargeable work begins. If you are unsure whether to attempt it yourself, our WordPress repair service starts with exactly that assessment.
Critical error versus a plugin simply misbehaving
Not every fault is critical. A plugin that displays a warning, hides a button or runs slowly is misbehaving but has not stopped WordPress. A critical error means execution halted. The distinction matters because the right response differs. A misbehaving plugin can usually be investigated calmly, while a critical error on a revenue-generating site needs a prompt, careful response. In both cases the same discipline applies: note what changed, secure a backup, read the logs and fix the cause rather than hiding the symptom. Resist the urge to delete plugin folders from the server, which removes evidence and settings together.
Getting help
If you are not sure which component is failing, or the site handles enquiries or orders, ask for help before experimenting. WP Mate investigates the error logs and recent changes, restores the failing function and explains the cause. Start with plugin error help or WordPress repair.
Want this looked after for you?
WP Mate maintenance plans cover managed updates, daily offsite backups, security scanning and 24/7 uptime monitoring.
Not sure what's wrong? Tell us and we'll outline the next step.
Services related to this guide
WordPress repair
Broken website? We investigate the cause and fix it safely.Get a Repair Quote →
Plugin error help
Plugin update broke something? We investigate safely.Get Plugin Error Help →
Talk to WP Mate
Not sure which service fits? Ask us and we will point you the right way.Contact us →
Related guides
Frequently asked questions
Is the WordPress critical error the same as the white screen of death?
They have the same cause, a fatal PHP error, but the critical error message is what WordPress shows when it manages to catch the error. The white screen appears when it cannot.
Can a critical error delete my website?
No. The error stops the website displaying, but your content normally remains in the database. Problems usually come from the fix attempts, not the error itself.
Why did the error appear after an update?
The update probably changed code that another part of your site depends on. Each website has its own mix of theme, plugins and PHP version, so an update that works elsewhere can fail on yours.
Ready to get your website sorted?
Based in Warrnambool, Victoria, helping Australian businesses online. Tell us what is happening.
Tell your mate what's going wrong.
Send us a few details and we’ll work out the next step. Please don’t include passwords or payment details.
- Australian support in plain English
- Clear scope and next steps before chargeable work
- Backup and recovery plan before live changes
