- Article
- Intermediate
- 2 minutes read
- Reviewed August 4, 2026
- WordPress maintenance and troubleshooting
A fatal PHP error can stop WordPress before it completes a request.
Visitors may see a critical-error message, a blank page, an HTTP 500 response or a host-specific error.
Preserve Access
Before changing files:
- Confirm a backup.
- record the error and time.
- preserve logs.
- identify the last deployment or update.
- open hosting, SFTP, SSH or control-panel access.
Use Recovery Mode
If WordPress sends a Recovery Mode email, use the protected session to inspect and pause the affected extension.
A missing email does not mean no fatal error occurred.
Enable Protected Logging
Configure debugging so errors are logged but not displayed publicly.
Review PHP and server logs when WordPress cannot create its own log.
Common Causes
- Plugin or theme syntax error.
- Unsupported PHP version.
- Missing class or function.
- Memory exhaustion.
- Failed update.
- Corrupted file.
- Dependency conflict.
- Database error.
- permissions.
- opcode cache serving stale code.
Manual Component Isolation
Rename a suspected plugin directory or use WP-CLI to deactivate it.
If no plugin is known, disable plugins in a controlled manner and switch to a default theme.
Restore Known-Good Code
Replace WordPress core with an official package when corruption is suspected.
Reinstall plugins and themes from trusted releases rather than editing vendor files blindly.
Frequently Asked Questions
Is a blank page always a memory problem?
No. It can result from any fatal error, output issue or server failure.
Should the error be hidden before it is fixed?
Hide detailed public output, but preserve protected logs for diagnosis.