Quick Diagnosis
Start with the most recent change. A critical error is usually a specific PHP fatal error, not a vague site-wide mystery.
Problem
Diagnose the WordPress critical error screen by checking recent plugin changes, PHP fatal errors, recovery mode, server logs, and safe rollback options.
Problem, cause, fix, verify
Problem
A PHP fatal error stopped WordPress before the page could render normally.
Audience
WordPress site owners and agencies responding to a sudden fatal error screen.
First check
Start with the most recent change. A critical error is usually a specific PHP fatal error, not a vague site-wide mystery.
Verify
Once wp-admin loads again, update or replace the failing component, remove temporary debug display, and confirm the same fatal error is not still appearing silently in logs.
Editorial trust
On this page
Symptom
For: WordPress site owners and agencies responding to a sudden fatal error screen.
Diagnosis
Start with the most recent change. A critical error is usually a specific PHP fatal error, not a vague site-wide mystery.
Avoid deleting plugins or database rows. Disable the suspected component and preserve evidence for the owner or developer.
Keep the recovery-mode email, PHP log excerpt, recent update list, plugin folder name, PHP version, and backup timestamp together. Those details help a developer fix the source instead of only reopening the site.
Once wp-admin loads again, update or replace the failing component, remove temporary debug display, and confirm the same fatal error is not still appearing silently in logs.
Diagnosis
Contact hosting support when logs are inaccessible, the site cannot be reached by SFTP, or PHP-level recovery is required.
Coverage
References