WordPress shows this message when a plugin, theme or code error crashes your site. Your content is almost always safe. Here's what it means and what to do.
What it means
This is WordPress's friendlier version of the white screen - instead of a blank page, you get a message saying something crashed. It means a PHP fatal error stopped WordPress from completing the request.
Why it happens
Same root causes as WSOD: plugin conflicts, theme incompatibility, memory limits, or bad code. The difference is WordPress managed to show its error page this time.
A real example
A photographer's portfolio site broke the morning after an automatic plugin update. Visitors saw "There has been a critical error on this website" while the admin area still loaded - because WordPress recovery mode had kicked in for the frontend only. The fatal error was a deprecated function in the theme that the updated plugin no longer tolerated. Recovery mode exists precisely for this: it lets an admin log in and deactivate the culprit without touching the database or files directly.
What to do
- Check the error details - WordPress often shows which plugin/theme is involved, or check the error log.
- Enable WP_DEBUG in wp-config.php for more detail if needed.
- Deactivate plugins one at a time (or rename the plugins folder) to isolate the culprit.
- Update WordPress core, theme, and plugins - the crash may already be patched.
Still stuck? Critical errors are recoverable - your content is in the database. We isolate the cause and restore the site.
Get emergency help