What causes a WordPress critical error?
The message is a safety screen, not a diagnosis. The actual cause is usually recorded in PHP or server logs. Common causes include an incompatible plugin, a theme function that fails, exhausted PHP memory, a PHP-version change, damaged core files, or an incomplete update.
I start by checking what the server is reporting. That avoids the risky cycle of changing random settings while the only usable copy of the site is already unstable.
Problems covered by this service
- “There has been a critical error on this website” messages
- White screen of death or completely blank pages
- HTTP 500, 502, or 503 responses tied to WordPress
- Broken wp-admin or login redirect loops
- A plugin, theme, WordPress, or PHP update that took the site down
- Maintenance mode that will not clear
- Fatal PHP errors and memory-limit failures
How the repair is handled
1. Preserve the best available copy
When access allows, I make or confirm a file and database backup before changing the broken installation.
2. Find the failing component
I review logs, recent changes, plugin and theme behavior, WordPress core integrity, database health, and hosting configuration. If emergency access is needed, changes are made at the file, database, or command-line level rather than relying on wp-admin.
3. Restore service and test the important paths
The repair includes checking the public site, admin access, forms or checkout where relevant, and the update state. I also explain what failed and identify any old component likely to cause the same problem again.
Do not keep retrying updates on the live site
If the site is down after an update, repeated attempts can overwrite evidence or leave the database and files at different versions. Send the URL and what changed; no password is needed for the first review.