What This Usually Means
This exact message usually points to one failing PHP execution path. The page may be down, but the useful fix still depends on the component named in recovery mode, PHP logs, or the most recent change.
Problem
Troubleshooting There Has Been a Critical Error on This Website
Recover from the WordPress critical error message by identifying the fatal error owner, preserving evidence, using recovery mode carefully, and verifying safe access.
Problem, cause, fix, verify
Problem
The message usually means WordPress hit a PHP fatal error before it could render the requested page, so the right fix depends on the recent change and the logged error.
Audience
WordPress site owners, administrators, developers, and agencies responding to the exact critical-error screen.
First check
This exact message usually points to one failing PHP execution path. The page may be down, but the useful fix still depends on the component named in recovery mode, PHP logs, or the most recent change.
Verify
WPlura Diagnostics can help structure the evidence and handoff notes, while Backup & Restore Manager supports the backup and restore-point review needed before destructive recovery work.
Editorial trust
- Publisher
- WPlura Editorial Team
- Published
- Updated
- Content type
- Problems
On this page
Symptom
The message usually means WordPress hit a PHP fatal error before it could render the requested page, so the right fix depends on the recent change and the logged error.
For: WordPress site owners, administrators, developers, and agencies responding to the exact critical-error screen.
Diagnosis
What to check before changing the site
Start With The Exact Request
The message is a symptom, not the diagnosis. The useful evidence is the URL or admin action that fails, the component mentioned in logs, and the change that happened just before the crash.
Map The Failure Surface
Separate public-page failures from wp-admin failures, editor-only crashes, checkout crashes, REST requests, scheduled events, and role-specific screens. That map usually tells you whether the owner is a plugin, theme, PHP runtime, custom snippet, host setting, or integration path.
Use Recovery Mode Carefully
Recovery mode can help regain wp-admin access, but it should not replace log review. Use it to disable the likely owner and keep notes on what changed.
Keep Debugging Private
WordPress debugging can record useful detail, but public error display is risky on production. Prefer private logs and turn temporary debugging back off after diagnosis.
Protect Live Data
If the error touches checkout, forms, memberships, LMS access, or customer accounts, check whether new orders, leads, users, or uploads were created after the last backup. A file rollback is often safer than a database restore when the fatal error belongs to code.
Rollback Boundary
A plugin or PHP rollback may restore access without touching the database. A full restore is a bigger decision because it may overwrite newer posts, orders, forms, users, or settings.
WPlura Fit
WPlura Diagnostics can help structure the evidence and handoff notes, while Backup & Restore Manager supports the backup and restore-point review needed before destructive recovery work.
WordPress ErrorsSeverity: HighLast reviewed: 2026-09-16
Diagnosis
Symptoms, causes, checks, and fixes
Symptoms
- The public page, wp-admin, or a specific admin screen shows “There has been a critical error on this website.”
- The site owner may receive a recovery-mode email after a plugin, theme, custom-code, PHP, or WordPress update.
- Some pages may still work while the failing request, editor screen, checkout path, or admin action crashes.
- The error may appear only for one user role, language, checkout step, editor screen, REST request, cron task, or product page because the failing code path is conditional.
Most Common Causes
- A plugin, theme, must-use plugin, custom snippet, or PHP version mismatch can throw a fatal error during request handling.
- A recent update can expose incompatible code, missing PHP extensions, memory exhaustion, or an autoload failure.
- Broad fixes such as deleting plugin folders or restoring the database too early can erase evidence and make rollback harder.
How To Confirm The Cause
- Write down the exact URL, admin action, user role, recent update, and whether the error affects public pages, wp-admin, or one workflow.
- Check the recovery-mode email if it arrived, then compare it with hosting PHP error logs or a safely configured WordPress debug log.
- Confirm whether SFTP, hosting file manager, or wp-admin plugin access is available before changing files or database state.
- Record the PHP version, WordPress version, active theme, must-use plugins, and the component named in the fatal error so the repair targets the owner instead of the whole site.
Fixes
- Disable only the confirmed failing plugin, theme, or custom snippet first; rename a plugin folder through SFTP only when wp-admin is unreachable.
- Restore the last known-good file version when custom code caused the fatal error, and avoid database restore unless the evidence points there.
- If the error started after a PHP change, confirm plugin/theme compatibility and roll back PHP through the host when that is the narrowest reversible fix.
How To Verify The Fix
- Reload the original failing URL and wp-admin screen from a fresh session after the narrow fix.
- Confirm logs stop recording the same fatal error and no debug output is exposed on public pages.
- Document the failed component, update or PHP version, final fix, backup state, and any deferred vendor or developer follow-up.
When To Contact Support
Escalate when logs are unavailable, the site cannot be reached by SFTP or hosting tools, the fatal error affects checkout or orders, or the fix requires editing PHP code you do not own.
Coverage
Related search intents
There Has Been A Critical Error On This WebsiteWordpress Critical Error MessageWordpress Critical Error Recovery ModeHow To Fix There Has Been A Critical Error On This WebsiteThere Has Been A Critical Error On This Website Troubleshooting
References