Encountering the “There has been a critical error on this website” message can be alarming—it often locks you out of your admin area and displays a blank page to visitors. This error, introduced in WordPress 5.2, indicates a PHP fatal error that halts site functionality. Common triggers include plugin conflicts, memory limits, or code issues, but the good news is it’s usually fixable without losing data. At Cope Business, we resolve these errors frequently during our technical SEO audit services, helping clients restore access and prevent recurrence. This 2026 guide explains the causes and provides step-by-step fixes to get your site back online quickly.
Whether you’re a beginner or experienced user, start with the simplest solutions and work your way down.
Common Causes of the Critical Error
- Plugin or Theme Conflicts: Incompatible or faulty code from recent updates.
- PHP Memory Exhaustion: Site exceeds allocated memory.
- Corrupted Core Files: Failed updates or hacks.
- Server Issues: Hosting problems like resource limits or misconfigurations.
- Custom Code Errors: Syntax mistakes in snippets or functions.
WordPress emails a recovery link to the admin—check your inbox first.
Step-by-Step Guide to Fixing the Critical Error
1. Use WordPress Recovery Mode
WordPress sends a recovery email with a link (e.g., /wp-login.php?action=enter_recovery_mode).
- Click the link to access recovery mode.
- Deactivate problematic plugins/themes from the dashboard.
- Exit recovery mode once resolved.
If no email arrives, fix email delivery with WP Mail SMTP.
2. Deactivate All Plugins
Plugins are the top culprit.
- Access via FTP (use FileZilla) or hosting file manager.
- Navigate to /wp-content/ and rename “plugins” to “plugins_old”.
- Reload your site—if it works, reactivate plugins one by one to find the issue.
- Update or replace the faulty plugin.
3. Switch to a Default Theme
Theme conflicts can crash sites.
- Via FTP, go to /wp-content/themes/ and rename your active theme folder.
- WordPress falls back to a default like Twenty Twenty-Six.
- If resolved, update or switch themes.
4. Increase PHP Memory Limit
Low memory causes fatal errors.
- Edit wp-config.php via FTP:
Add define('WP_MEMORY_LIMIT', '256M'); before the "stop editing" line.- Save and reload.
- If ineffective, contact your host to raise server limits.
5. Enable Debugging and Check Error Logs
Uncover the exact cause.
- In wp-config.php, set
define('WP_DEBUG', true); define('WP_DEBUG_LOG', true); define('WP_DEBUG_DISPLAY', false);.- Reload the site—errors log to /wp-content/debug.log.
- Review the log for clues (e.g., plugin names).
- Fix the indicated issue and disable debugging.
6. Reinstall WordPress Core Files
Corrupted files from failed updates.
- Download the latest WordPress zip from wordpress.org.
- Unzip and upload all folders/files except wp-content (overwrite existing).
- Run /wp-admin/upgrade.php if prompted.
7. Restore from Backup
If other fixes fail.
- Use your backup plugin (e.g., UpdraftPlus) or hosting backup.
- Restore to a previous working state.
- Test and identify what caused the error (e.g., recent update).
8. Contact Your Hosting Provider
Server-side issues like mod_security rules or resource caps.
- Provide error details from logs.
- Ask them to check server errors or whitelist your IP.
Preventing Future Critical Errors
- Enable auto-updates for minor releases.
- Test updates on staging first.
- Use reliable plugins/themes from trusted sources.
- Regular backups and security scans (Wordfence recommended).
- Monitor with tools like Site Health.
Most errors resolve with plugin deactivation or memory increases—start there.
Facing this error or need proactive prevention? Contact Cope Business for a free technical SEO audit—we’ll diagnose the issue and optimize your site for reliability.
