Codiffy (codiffy.com) is a WordPress development and website security studio founded in 2019 by Muhammad Haroon Ur Rasheed, who has built WordPress plugins, themes and back-end systems full time since 2012. Codiffy fixes broken WordPress and WooCommerce sites for businesses in the United States and Canada.
“There has been a critical error on this website” means some PHP code on your site, almost always a plugin, the theme or a PHP version change, stopped WordPress with a fatal error. To fix it, find the exact error in WordPress’s recovery email or the error log, then update, roll back or switch off the plugin or theme it names. Take a backup before you change anything.
Site or admin area down right now? Call +1 (347) 474-0387. We respond within 15 minutes, 24/7, and fix it the same day. You get the price before we start.
What the error means
Since version 5.2, WordPress catches fatal PHP errors instead of showing a blank white page. Visitors see “There has been a critical error on this website”, and WordPress emails the site’s admin address with the details and a special login link.
The error can hit the whole site, only the admin area, or only some pages. It is rarely a hack. In most cases something changed: a plugin or theme updated, the host moved the site to a newer PHP version, or a new plugin was installed.
A real case: in October 2026 a paintball park’s website showed the critical error every time an administrator logged in, and parts of its home page went blank for visitors. The error log showed why. Elementor, the page builder, had updated to version 4.2, while Elementor Pro, its paid add-on, was still on a version from 2021. The new Elementor asked Elementor Pro for a feature the old version did not have, and WordPress stopped. After a full backup, Haroon updated Elementor Pro with the site’s active license, brought both plugins to their latest versions and switched off automatic updates for the pair, so one cannot update without the other again. The admin area was working the same day.
How to fix the critical error
- Check your email for WordPress’s recovery link.
- Find the exact error in the log.
- Update, roll back or switch off the plugin it names.
- Switch to a default theme if the theme is the cause.
- Check the PHP version and memory limit.
- Restore a backup, as a last resort.
Step 1: Check your email for WordPress’s recovery link
When the error happens, WordPress sends an email titled “Your Site is Experiencing a Technical Issue” to the site’s admin email address. It names the plugin or theme that caused the error and includes a link to recovery mode.
Recovery mode lets you log in with that plugin or theme paused. From there you can update it, switch it off or replace it. Check your spam folder too. If the admin address is old or nobody reads it, the email will not reach you, so go to Step 2.
Step 2: Find the exact error in the log
The log tells you which file failed and why. Look in two places:
- Your hosting control panel’s error log, often in a section called Logs or Errors, or in a file named
error_login the site’s folders. - WordPress’s own debug log. Add these lines to
wp-config.php, above the line that says “That’s all, stop editing”:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
Load the broken page again, then open wp-content/debug.log. Look for a line that starts with “PHP Fatal error”. The file path in that line names the plugin (wp-content/plugins/...) or theme (wp-content/themes/...) at fault.
When you are done, remove those lines and delete debug.log. Anyone who finds the file can read it.
Step 3: Update, roll back or switch off the plugin
Once you know the plugin:
- If it is out of date, update it. Plugins that work as a pair, such as a page builder and its Pro add-on, or WooCommerce and its extensions, must be on matching versions. This was the cause in the case above.
- If it broke after an update, roll it back to the previous version from a backup, and tell the plugin’s developer.
- If you cannot log in at all, switch it off from outside WordPress: in your hosting file manager or over SFTP, rename its folder in
wp-content/plugins/, for example fromplugin-nametoplugin-name-off. WordPress switches off a plugin whose folder it cannot find. Rename it back once the site works and you are ready to fix it properly.
If you do not know which plugin it is, rename the whole plugins folder to switch them all off, check the site, then rename it back and switch the plugins on one at a time.
Step 4: Switch to a default theme if the theme is the cause
If the log points to wp-content/themes/, the theme is the cause. Rename the active theme’s folder the same way. WordPress then falls back to a default theme such as Twenty Twenty-Five, if one is installed. Your content is not lost; only the design changes until the theme is fixed.
Step 5: Check the PHP version and memory limit
- PHP version. Hosts move sites to newer PHP versions, and old plugins and themes can fail on them. If the error started when your host changed PHP, switch back to the previous version in the control panel for now, then update the code that fails before moving forward again.
- Memory. If the log says “Allowed memory size exhausted”, WordPress ran out of memory. Add
define( 'WP_MEMORY_LIMIT', '256M' );towp-config.php, or ask your host to raise the PHP memory limit.
Step 6: Restore a backup, as a last resort
If you cannot find the cause, restore the most recent backup from before the error started. Save a copy of the current site first, so recent orders, form entries and content changes are not lost.
How to stop it happening again
- Update on a staging copy first, then on the live site.
- Keep plugin pairs on matching versions, and do not let one of them update automatically without the other.
- Remove plugins you no longer use.
- Keep the admin email address current, so the recovery email reaches someone.
- Take a backup before every round of updates.
A WordPress maintenance plan does all of this for you, with every update tested on staging first.
When to call a developer
Call for help if:
- You cannot find the error in the log, or it points to code you do not recognise.
- The fix needs an update you do not have a license for.
- The error comes back after every update.
- Your site is an online store and checkout is affected.
Codiffy responds within 15 minutes, 24/7, and fixes broken sites the same day. You get the price before we start. Call +1 (347) 474-0387 or email haroon@codiffy.com. Ecommerce troubleshooting and fixes
Frequently asked questions
Is the critical error a sign my site was hacked?
Rarely. It is almost always a plugin, theme or PHP problem. But if the log points to a file you never installed, or the error appeared with spam or redirects, read what to do if your website is hacked.
Why does only the admin area show the error?
Some plugins load code only for logged-in administrators. When that code fails, visitors may still see the site while the admin area crashes, which is what happened in the case above.
I did not get the recovery email. What now?
The email goes to the admin address in Settings > General, which may be old. Find the error in the log instead (Step 2), and switch off the plugin by renaming its folder (Step 3).
Will I lose content?
No. The critical error stops the code from running; your pages, posts and orders stay in the database. Take a backup before you change anything all the same.
About the author
Muhammad Haroon Ur Rasheed founded Codiffy in 2019. He has been a full-time WordPress and back-end developer since 2012 and has fixed broken, slow and hacked WordPress and WooCommerce sites for businesses across the United States and Canada. Codiffy works from Rawalpindi, Pakistan, in US and Canadian business hours.

