Last Updated on Nov 5, 2026 by Nurul Afsar
Seeing “There has been a critical error on this website” can be alarming, especially when your WordPress dashboard also stops loading. The message tells you something failed, but it does not explain what needs fixing.
To fix the critical error in WordPress, check the administrator email for a Recovery Mode link, identify the fatal error, and disable or repair the responsible component. When Recovery Mode is unavailable, your hosting error logs and file manager can help you investigate without dashboard access.
In this guide, we’ll explain what causes WordPress critical errors, how to restore access to your website, and how to prevent similar issues from happening again.
Important Disclaimer: Read Before Making Changes
This guide is for informational purposes only. Readers are responsible for any changes they make to their websites. Editing WordPress files, plugins, or server settings can cause downtime, data loss, or other technical issues.
Always back up your website and test changes in a staging environment. We recommend consulting a senior web developer, your in-house technical team, or qualified WordPress experts before attempting unfamiliar procedures.
Numinix cannot guarantee results and, to the extent permitted by law, is not responsible for losses resulting from readers independently following these instructions.
Need Professional WordPress Help?
Let Numinix help troubleshoot critical errors, plugin conflicts, and website crashes.
Get Expert Help & Request a Quote →Repairs, custom work, and third-party licenses may involve additional costs.
What Does the WordPress Critical Error Mean?
A WordPress critical error generally means a fatal PHP error interrupted the request. WordPress displays this message instead of exposing sensitive technical details to website visitors.
Common causes include:
- Plugin conflicts: Incompatible or malfunctioning plugins can trigger fatal errors.
- Theme problems: Faulty theme code or incompatible updates may prevent pages from loading.
- PHP compatibility: Plugins or themes may not support the PHP version used by your hosting server.
- Insufficient memory: Resource-intensive operations can exhaust available PHP memory.
- Failed updates: Interrupted WordPress, plugin, or theme updates may leave files incomplete.
- Custom code errors: Invalid code in functions.php or custom snippets can break website functionality.
The message alone does not prove that your website was hacked or that its content was deleted. Your error logs provide the evidence needed to choose an appropriate fix.
A generic HTTP 500 response can have additional server-side causes. Our 500 Internal Server Error troubleshooting guide covers those situations in more detail.
Before Making Changes to Your WordPress Website
Record when the critical error started and what changed immediately beforehand. If you recently updated a plugin, switched themes, or modified PHP settings, that information can help narrow down the problem.
Create a current backup of your website files and database, even if the website is broken. Preserve any earlier working backups as well.
Whenever possible, use a staging environment to test potentially disruptive changes before applying them to your live website.
How to Fix the Critical Error in WordPress: Step by Step
1. Check Your Administrator Email and Enter Recovery Mode
WordPress includes a Recovery Mode feature that can help administrators investigate certain fatal errors.
Check your site’s administration email inbox and spam folder for a WordPress message about a technical issue. The email may identify the failing plugin or theme and include a special Recovery Mode login link.
To use Recovery Mode:
- Open the recovery email from WordPress.
- Follow the private Recovery Mode link.
- Sign in to your WordPress dashboard.
- Review the notices identifying the problematic component.
- Deactivate or repair the affected plugin or theme.
- Test the website again.
Important: Recovery Mode pauses the faulty component only for your recovery session. Visitors may still encounter the error until the underlying problem is fixed.
Exit Recovery Mode and check the public website afterward.
If you’re experiencing a WordPress critical error with no email, continue with the following troubleshooting methods. Email delivery problems can prevent recovery messages from reaching administrators.
2. Enable WordPress Debugging and Check Error Logs
WordPress debugging can help identify which PHP error is responsible for the failure.
Start by checking your hosting provider’s PHP error logs. These may already contain the information needed to identify the issue.
If additional debugging is necessary, access your website files through SFTP or your hosting file manager and locate the wp-config.php file.
On a staging website, you can configure debugging with the following values:
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);
@ini_set('display_errors', 0);Add or update these settings before the line indicating that WordPress configuration editing is complete. Modify existing definitions rather than creating duplicates.
After reproducing the error, check the /wp-content/debug.log file, if your installation is configured to write logs there.
Look for messages such as:
- PHP Fatal error
- Allowed memory size exhausted
- Call to undefined function
- Parse error
- Uncaught Error or TypeError
The log may reference a particular plugin, theme, or WordPress file. Use this information to investigate the source of the problem.
Because debugging logs can contain sensitive information, restrict access to them and disable debugging after troubleshooting.
3. Disable WordPress Plugins Without Dashboard Access
Plugin conflicts are among the common causes of WordPress critical errors.
If the error message identifies a plugin and you cannot access wp-admin, you can temporarily disable it through your hosting file manager or SFTP.
- Connect to your website files.
- Navigate to
/wp-content/plugins/. - Find the folder belonging to the suspected plugin.
- Rename the folder, such as from
example-plugintoexample-plugin-disabled. - Try accessing your WordPress dashboard again.
If dashboard access returns, visit Plugins > Installed Plugins so WordPress can recognize the missing plugin as deactivated.
You can then restore the original folder name, but leave the plugin inactive until its underlying problem is resolved.
If multiple plugins may be involved, investigate conflicts in a staging environment. Disable and reactivate the relevant plugins individually while testing the affected functionality.
For ecommerce websites, avoid indiscriminately disabling payment gateways, checkout extensions, security plugins, or other business-critical components on the live store.
4. Check Your WordPress Theme and Custom Code
A WordPress critical error after an update may involve your active theme or child theme rather than a plugin.
Recent changes to functions.php, custom snippets, or theme templates can also introduce PHP errors.
If you can access the dashboard, navigate to Appearance > Themes and temporarily activate an installed, compatible default WordPress theme on your staging website.
If the error disappears, investigate the original theme’s recent updates, customizations, and compatibility requirements.
When dashboard access is unavailable, ask your hosting provider or developer to help activate a known-good theme.
Do not delete theme folders or assume renaming a theme will work without a valid replacement.
5. Check PHP Compatibility and Memory Limits
WordPress themes and plugins depend on PHP to execute their code. Using an incompatible PHP version can cause unexpected failures.
Review the PHP version running on your hosting account and compare it with the requirements of WordPress, your theme, and installed plugins.
Once your dashboard is accessible, you can find additional server information under Tools > Site Health > Info.
If the error log reports exhausted memory, investigate the operation responsible for consuming resources.
Your hosting provider may recommend increasing the PHP memory limit, but additional memory will not resolve defective code or every resource-related problem.
When adjusting PHP versions or memory settings, change one configuration at a time and test the affected functionality afterward.
6. Investigate Failed WordPress Updates or Damaged Files
If the critical error appeared immediately after a WordPress update, some files may have become incomplete or inconsistent.
Ask your hosting provider or developer to inspect the installation and determine whether affected components need to be reinstalled.
When restoring WordPress core files, preserve your website’s database, wp-config.php, uploaded media, and custom content.
Always obtain replacement files from trusted, official sources.
If your website also shows suspicious redirects, unfamiliar administrator accounts, or unexpected file modifications, the problem may require a security investigation.
Numinix provides WordPress malware removal services for businesses dealing with compromised websites and suspicious activity.
Should You Restore a WordPress Backup?
Restoring a verified backup from before the incident may be appropriate when targeted repairs are unsuccessful.
However, restoring an older backup can overwrite changes made after that backup was created.
This is particularly important for WooCommerce websites, where recent orders, customer registrations, and inventory updates may exist only in the current database.
Before restoring a backup, preserve the current website state and determine whether a targeted file repair could resolve the problem without replacing valuable transaction data.
After recovery, investigate the original cause before attempting the same update again.
How to Confirm Your WordPress Website Is Working Again
Once the critical error disappears, verify that the website functions normally rather than relying only on the homepage loading successfully.
Test the following areas:
- Homepage and important landing pages.
- WordPress administrator login.
- Contact forms and form submissions.
- Navigation menus and interactive features.
- Product pages and variation selectors.
- Shopping cart and checkout functionality.
- Order confirmation and customer notifications.
For WooCommerce stores, perform payment testing in an appropriate sandbox or staging environment.
Our article on safer WordPress and WooCommerce update testing explains how testing environments can help reduce the risk of introducing new problems.
How to Prevent WordPress Critical Errors
Although not every technical failure is preventable, a consistent maintenance process can reduce unexpected downtime.
- Maintain reliable backups: Keep recoverable copies of your website files and database.
- Test updates: Evaluate major plugin, theme, and WordPress changes before production deployment.
- Monitor compatibility: Check PHP requirements and plugin dependencies before upgrading.
- Remove unnecessary extensions: Reduce the number of plugins requiring maintenance.
- Review error logs: Investigate recurring warnings and failures.
- Monitor important functionality: Regularly check forms, checkout, payments, and custom integrations.
For business-critical websites, professional maintenance and technical monitoring can help identify potential problems before they result in prolonged downtime.
Frequently Asked Questions About WordPress Critical Errors
Why did my WordPress site suddenly show a critical error?
A plugin update, theme change, custom code modification, or hosting configuration change may have introduced a fatal PHP error. Review recent changes and server logs to identify the cause.
Can I fix a WordPress critical error without admin access?
Yes. Depending on the problem, you may be able to use WordPress Recovery Mode, your hosting file manager, or SFTP to disable the affected component and restore access.
What should I do if WordPress does not send a recovery email?
Check the administrator email address and spam folder. If no recovery email arrives, investigate your hosting error logs and use file-level troubleshooting methods.
Will clearing the WordPress cache fix a critical error?
Clearing cached pages does not repair broken PHP code. However, it may remove a previously cached error page after the underlying problem has been resolved.
Will fixing the WordPress critical error delete my content?
Disabling a malfunctioning plugin does not normally delete posts and pages. However, reinstalling components or restoring an older backup can affect website data. Preserve backups before proceeding.
Get Professional Help Fixing WordPress Critical Errors
A WordPress critical error can interrupt customer enquiries, website operations, and online sales. Identifying the underlying cause is essential to restoring functionality and reducing the risk of repeated failures.
At Numinix, we help businesses investigate WordPress errors, troubleshoot plugin conflicts, address website crashes, and improve technical stability.
Explore our WordPress and WooCommerce crash troubleshooting services or learn more about our WooCommerce development services for websites requiring additional customization and technical support.
If your website is experiencing repeated critical errors, our team can review your requirements and recommend an appropriate solution.
Request a Free Consultation and Custom Quote
Service scope: Technical repairs, custom development, premium plugin licenses, third-party fees, and ongoing maintenance are included only when specified in your proposal. Final scope and pricing depend on the assessment.