Few things spike a business owner’s heart rate like opening their own website and seeing: “There has been a critical error on this website.” The good news: this error is rarely fatal, and in most cases your site is back within the hour.
What the error actually means
WordPress shows this message when a piece of PHP code crashes — almost always inside a plugin or theme. Your content, orders and images are all still there. Something in the code just tripped, and WordPress hid the details from visitors on purpose.
Step 1: Check your email
Since version 5.2, WordPress emails the site admin when this happens. Search your inbox for “Your site is experiencing a technical issue”. That email names the exact plugin or theme at fault and includes a special recovery-mode link. If you have it, click it, deactivate the named plugin, and you’re done.
Step 2: Deactivate plugins without the email
No email? You can still get in:
- Log in to your hosting control panel and open the file manager (or connect with FTP).
- Navigate to
wp-contentand rename thepluginsfolder toplugins-off. - Load your site. If it works, a plugin was the culprit.
- Rename the folder back, then rename individual plugin folders one at a time until you find the guilty one.
Step 3: Switch to a default theme
If plugins aren’t the problem, rename your active theme’s folder inside wp-content/themes. WordPress will fall back to a default theme. If the site comes back, the error lives in your theme — often after an update or a manual edit.
Step 4: Raise the memory limit
Occasionally the cause is simply memory. Add this line to wp-config.php above the “stop editing” comment: define( 'WP_MEMORY_LIMIT', '256M' );
How to stop it happening again
Almost every critical error we see comes from the same place: updates applied blind, with no backup and no one watching. Update plugins one at a time, keep daily backups, and remove plugins you don’t use.