To fix “There has been a critical error on this website,” first check the WordPress recovery email and server error log, then isolate the plugin, theme, custom-code, PHP, or memory problem that triggered the fatal error. Do not reinstall WordPress or delete content before you identify the cause.

What the WordPress Critical Error Means

The message is WordPress’s user-friendly response to a fatal PHP error. Common triggers include an incompatible plugin update, a broken theme function, unsupported PHP syntax, exhausted memory, missing files, or custom code that calls an unavailable function. Your database content is usually still intact.

1. Use WordPress Recovery Mode

WordPress may email the site administrator a recovery link that temporarily pauses the faulty extension for your session. Check spam and confirm the address under Settings → General. Log in through the secure link, note which component failed, create a backup, and update, replace, or deactivate that component.

2. Read the Error Log

The log usually identifies the exact file and line. Your host may expose PHP logs in its control panel. You can also enable WordPress logging temporarily by adding these constants above the “stop editing” line in wp-config.php:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

Reproduce the problem once, then inspect wp-content/debug.log. Turn debugging off after diagnosis and never display errors publicly on a production site.

3. Isolate Plugins Without Dashboard Access

Using your host’s file manager or SFTP, rename wp-content/plugins to plugins-disabled. If the site loads, restore the directory name and rename individual plugin folders until you find the failure. WP-CLI users can deactivate plugins from the command line, but should preserve a list of the original active plugins first.

Once identified, update the plugin, revert the most recent version, or contact its vendor with the fatal-error text. Do not keep an abandoned or vulnerable release active merely because it avoids the error.

4. Test the Active Theme

If plugins are not responsible, activate a current default WordPress theme. Without dashboard access, rename the active theme directory only after confirming a default theme is installed. If the site returns, review recent edits to functions.php, template overrides, and theme dependencies.

5. Check PHP Version, Memory, and Files

• PHP version: compare the host’s PHP release with requirements for WordPress, the theme, and every critical plugin.
• Memory: an “allowed memory size exhausted” log entry points to a resource problem or inefficient code.
• Files: replace damaged WordPress core files using a clean package while preserving wp-content and wp-config.php.
• Permissions: verify that the web server can read required files without making directories unnecessarily writable.

If the message mentions database drivers, follow our dedicated guide to the missing MySQL extension error.

Prevent the Error From Returning

Use staging for updates, keep automated off-site backups, remove unused extensions, monitor PHP logs, and avoid pasting unreviewed snippets into production. Update one controlled batch at a time so you can connect a new failure to a specific change.

Critical Error FAQ

Can I fix the error without losing content?

Usually, yes. Plugin and theme failures rarely delete posts. Back up first, diagnose from logs, and avoid resetting the database.

Why does only one page show the error?

That page may execute a specific block, shortcode, template, or plugin function. Its URL and corresponding log entry narrow the investigation.