A WordPress critical error can prevent visitors from accessing your website and may even lock you out of the administration dashboard. This problem often appears after installing a plugin, updating a theme, changing PHP code, or upgrading the PHP version. Although the message can look serious, the underlying cause is usually identifiable through a systematic troubleshooting process.
What Causes a WordPress Critical Error?
WordPress relies on PHP to execute themes, plugins, and core functionality. If a PHP error interrupts execution, WordPress may display a message stating that a critical error has occurred.
Common causes include incompatible plugins, outdated themes, PHP syntax errors, insufficient server resources, and conflicts between different components. Custom code added through a snippets plugin can also cause fatal errors, particularly when a function is declared twice or references an unavailable class.
Step 1: Check Your Email for Recovery Instructions
WordPress may send an administrator an email containing information about the critical error. Depending on the error and WordPress configuration, the message can identify the affected plugin or theme and provide a recovery link.
Open the email and review the reported component. If WordPress offers Recovery Mode, use it to access the dashboard and deactivate the problematic component.
If no email arrives, continue with the following steps.
Step 2: Disable Plugins Through Your Hosting Account
If the dashboard is inaccessible, open your hosting control panel and navigate to the website’s files using File Manager or FTP.
Locate the wp-content directory and rename the plugins folder to something like plugins-disabled. This temporarily prevents WordPress from loading the installed plugins.
Check whether the website becomes accessible. If it does, restore the original folder name and deactivate plugins individually to identify the cause. This method may affect plugin-dependent functionality while troubleshooting.
Step 3: Switch to a Default Theme
If disabling plugins does not resolve the problem, investigate the active theme.
Use File Manager or FTP to access wp-content/themes. If a compatible default WordPress theme is already installed, temporarily rename the active theme’s directory. WordPress may switch to an available default theme.
Avoid deleting the theme because doing so can remove important files or complicate recovery. If the error disappears, inspect the theme’s recent updates and custom PHP modifications.
Step 4: Enable Error Logging
For deeper investigation, enable WordPress debugging in wp-config.php. Back up the file first and place the following settings before the line that says to stop editing:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );If these constants already exist, modify their existing values instead of defining them again. Reproduce the error and inspect wp-content/debug.log, if the server permits WordPress to write the file.
Disable debugging when the investigation is complete. Logs can contain sensitive information and should never be publicly exposed.
Step 5: Restore the Website Safely
Once you identify the cause, update or replace the incompatible component, correct the faulty code, or restore a known-good backup if necessary. Test the homepage, administration dashboard, forms, and checkout process before considering the recovery complete.
Final Thoughts
The safest approach is to isolate the problem before making permanent changes. Start with recovery instructions, then test plugins, themes, and logs in a controlled order. Always maintain a current backup, and avoid editing production files without a recovery plan.