WordPress Critical Error
Your website suddenly shows “There has been a critical error on this website,” or a blank white page, often right after an update. Customers can't reach you and you may be locked out of the dashboard. A Codersarts WordPress engineer finds what broke and gets your site back online safely.
The WordPress critical error message means PHP hit a fatal error while loading your site. The usual triggers are a plugin or theme update that conflicts with something else, a hosting upgrade to a newer PHP version that an older plugin doesn't support, the site running out of PHP memory, corrupted files from an interrupted update, or a mistake in custom code. WordPress hides the details from visitors, but the error log names the exact file responsible.
Typical symptoms | Critical error message, white screen, admin dashboard locked, errors right after an update |
Most common causes | Plugin or theme conflicts, PHP version incompatibility, memory limits, failed updates, custom code errors |
How we fix it | Read the error log, isolate the failing plugin or theme, repair or replace it, test on a safe copy of the site |
Turnaround | Same-day diagnosis; most fixes in 24–48 hours |
Price | Live Debug from $20; fixed-price quote for the full fix |
Signs Your WordPress Site Has This Problem
The site shows There has been a critical error on this website
Visitors see a blank white page instead of your site
You can't log in to the WordPress dashboard
The error started right after updating a plugin, theme, or WordPress itself
Your host recently upgraded the site's PHP version
You received an email from WordPress about a technical issue on your site
Only some pages, such as checkout or a contact form, show the error
Why WordPress Shows a Critical Error
WordPress runs on PHP, and every plugin and theme adds its own PHP code. When any piece of that code fails badly enough, WordPress stops loading and shows the generic critical error message instead of your site.
1. A plugin or theme conflict
An update to one plugin can clash with another plugin, your theme, or WordPress itself. This is the most common cause, especially when several updates run at once.
2. A PHP version the code doesn't support
Hosting companies regularly move sites to newer PHP versions. Older or abandoned plugins and themes that use outdated PHP code can fail immediately after the upgrade.
3. Running out of memory
Heavy plugins, page builders, and large stores can exceed the PHP memory limit. The error log shows a message about allowed memory size being exhausted.
4. Corrupted files from a failed update
If an update times out or is interrupted, WordPress core, plugin, or theme files can be left incomplete, which breaks the site on the next load.
5. Custom code errors
Snippets added to the theme's functions file or a custom plugin can contain errors that only appear on certain pages or after other updates.
How We Diagnose the Critical Error
Use WordPress recovery mode. Check the site admin email for the recovery link WordPress sends, which can reveal the failing plugin or theme.
Read the error log. Enable WordPress debug logging safely, or check the hosting PHP error log, to find the exact file and line.
Isolate plugins. Deactivate plugins through file access or the database when the dashboard is locked, then reactivate them one at a time.
Test the theme. Temporarily switch to a default theme to confirm or rule out the theme.
Check PHP version and memory. Compare the current PHP version and memory limit with what your plugins and theme require.
Scan for tampering. Check for unexpected file changes, since malware can also cause fatal errors.
How We Fix It
Root cause | Fix |
Plugin or theme conflict | Roll back, update, or replace the conflicting plugin, and fix the incompatibility if you depend on it |
PHP version incompatibility | Update or replace outdated code so the site runs safely on a supported PHP version |
Memory exhausted | Raise the memory limit appropriately and reduce what's consuming memory |
Corrupted files | Reinstall clean copies of WordPress core, plugins, or themes without touching your content |
Custom code error | Correct the code and move snippets into a safe, maintainable location |
No safe way to update | Set up a staging copy of the site so future updates are tested before going live |
We fix the problem without losing your content, orders, or settings, and back up the site before making changes.
Example Fix
Situation: A service business's WordPress site went down with a critical error the morning after automatic updates ran, and the owner was locked out of the dashboard.
Cause: A form plugin update required a newer PHP version than the hosting account used, and it also conflicted with an old page builder add-on.
Fix: Rolled back the form plugin, moved the site to a supported PHP version on a staging copy, replaced the abandoned add-on, and then re-applied updates in a tested order.
Result: The site was back online the same day, forms worked again, and future updates were tested on staging first.
How to Keep It From Happening Again
Test updates on a staging copy before applying them to your live site.
Remove abandoned plugins that haven't been updated in a long time.
Keep daily backups stored outside your hosting account so you can restore quickly.
What You Get
Site restored and working
Cause of the error explained in plain language
Conflicting or outdated code repaired or replaced
Recommendations for safe future updates
Frequently Asked Questions
What does “There has been a critical error on this website” mean?
WordPress hit a fatal PHP error while loading your site. It's usually caused by a plugin, theme, PHP version change, or memory limit, and the error log shows which one.
Will I lose my content if I fix the critical error?
No. The error is in code, not your content. Posts, pages, orders, and settings are stored in the database and stay intact during a proper fix.
How do I fix a WordPress critical error if I can't log in?
Plugins and themes can be disabled through file access or the database without the dashboard. WordPress may also email the site admin a recovery mode link.
Why did the error appear after my host upgraded PHP?
Older plugins and themes can use code that newer PHP versions no longer support. Updating or replacing that code resolves it.
Could my site have been hacked?
Sometimes. Malware can cause fatal errors, so we check for unexpected file changes while diagnosing the issue.
Related Problems
WordPress site suddenly slow
WordPress site left unfinished
Freelancer delivered broken code
Stripe webhook not working
Get Your Website Back Online
Share your site address and when the error started. Get a diagnosis and a fixed price.