WordPress Website Showing a Critical Error? 9 Fixes for UK Businesses

wordpress-critical-error-fixes

You open your business website and discover that customers can no longer access it. Instead of your homepage, WordPress displays: "There has been a critical error on this website."

A WordPress critical error usually means that the website has encountered a fatal PHP error that prevents part of the application from running. Possible causes include incompatible plugins, faulty themes, PHP version changes, custom code mistakes, memory exhaustion, incomplete updates or server configuration problems.

The error may affect your public website, individual pages or the WordPress dashboard.

The safest first step is to identify what failed, preserve your website data and investigate the evidence before changing anything.

What Does "There Has Been a Critical Error on This Website" Mean?

WordPress includes a fatal error protection mechanism designed to detect certain serious application errors.

When the system detects a qualifying PHP fatal error, it may display a simplified message instead of revealing technical information to visitors.

WordPress may also email the website's administration address with details of the error and a special Recovery Mode link.

This protects visitors from seeing potentially sensitive technical information, including internal file paths.

However, several website errors can look similar:

ErrorWhat it generally indicates
WordPress critical errorWordPress has detected a serious PHP application error
White Screen of DeathThe website displays a blank page, potentially because of a PHP error
HTTP 500 errorThe server encountered a problem processing the request
Database connection errorWordPress cannot establish the required database connection
Hosting outageThe web server or supporting infrastructure is unavailable

These problems sometimes overlap, but they do not necessarily have the same cause.

A critical error message is a symptom. Determining the underlying cause requires checking recent changes, recovery notifications and relevant error logs.

What Should You Do Before Trying to Fix a WordPress Critical Error?

Rushing to reinstall WordPress or deactivate every plugin could create additional problems.

Before attempting repairs:

  1. Record when the problem started. Check whether it followed a plugin update, PHP upgrade, theme change, migration or code modification.
  2. Identify affected areas. Test the homepage, important internal pages and /wp-admin/.
  3. Check the administrator email. Look for a WordPress technical issue notification, including in spam or quarantine folders.
  4. Preserve the current website. Where possible, create a fresh backup of website files and the database, even if the site is already broken.
  5. Check existing backups. Confirm that a previous backup is complete and understand what would be lost during restoration.
  6. Contact your hosting provider when appropriate. Ask about recent server changes, error logs and available recovery snapshots.

Avoid deleting WordPress directories, installing unfamiliar repair scripts or changing PHP settings without evidence.

For ecommerce or booking websites, extra care is essential. Restoring an older database might overwrite orders, appointments or enquiries received after the backup was created.

9 Ways to Fix a WordPress Critical Error

The following solutions address different causes. Start with the evidence most relevant to your website rather than applying every fix.

Fix 1: Use WordPress Recovery Mode to Identify the Problem

Typical symptoms: Your website displays a critical error, but WordPress has detected a faulty plugin or theme and generated a recovery notification.

Recovery Mode can temporarily pause the affected component for an administrator's recovery session.

Check the website's administration email for a message titled similarly to "Your Site is Experiencing a Technical Issue".

Open its Recovery Mode link, sign in and review the dashboard notices.

If WordPress identifies a problematic plugin or theme, investigate that component before making a permanent change.

Once the fault has been corrected, exit Recovery Mode and test the website outside the recovery session.

What if the recovery email never arrives?

Check the configured administrator mailbox, spam filtering and email delivery settings. An error occurring before the normal email delivery system loads can also prevent the notification from reaching you.

Recovery links can expire, and errors in background processes may not activate the same recovery mechanism.

If Recovery Mode remains unavailable, use hosting logs or request assistance.

Remember: Recovery Mode provides diagnostic access. It does not permanently repair faulty code.

Fix 2: Investigate Faulty or Incompatible WordPress Plugins

Typical symptoms: A critical error appears immediately after installing, updating or activating a plugin.

Plugins execute PHP code alongside WordPress. An outdated extension, incompatible dependency or conflicting integration can cause a fatal error.

Start by checking the recovery notification or server error log for references to /wp-content/plugins/.

If the evidence identifies a particular plugin, make a backup and deactivate that component through the dashboard or Recovery Mode.

When the dashboard is unavailable, a qualified administrator may temporarily rename the specific plugin directory using a secure hosting file manager or SFTP.

Test the affected functionality afterwards.

A permanent fix may require a compatible update, corrected configuration, vendor support or replacement plugin.

Avoid disabling every production plugin without assessing dependencies. WooCommerce, payment gateways, membership systems and booking extensions may be essential to business operations.

If the problem involves customised integrations or returns after reactivation, ask a WordPress developer to investigate.

Fix 3: Check Whether Your WordPress Theme Is Causing the Error

Typical symptoms: The website breaks following a theme update, design change or modification to a child theme.

Themes can contain PHP functions, templates and integrations that become incompatible with newer WordPress or PHP versions.

Review error logs for references to /wp-content/themes/, particularly files associated with the active theme.

A developer can investigate the relevant file and reproduce the issue on a staging website.

Testing a compatible default WordPress theme may help determine whether the active theme contributes to the problem.

However, switching themes can change layouts, navigation, custom functionality and storefront behaviour.

Do not switch a live ecommerce theme without understanding the potential customer impact.

When custom functions or child theme modifications are involved, correcting the affected code is normally preferable to replacing the entire design.

Fix 4: Resolve PHP Version or Extension Compatibility Problems

Typical symptoms: WordPress stops working after a hosting migration, PHP upgrade or server configuration change.

WordPress, themes and plugins depend on a compatible PHP environment.

The latest WordPress hosting recommendations should be checked alongside the requirements of installed extensions and custom code.

Relevant errors may contain phrases such as:

  • Call to undefined function
  • Uncaught Error
  • Declaration of ... must be compatible

These messages require interpretation in context. A missing function could indicate an unavailable PHP extension, a dependency problem or incompatible application code.

Check the PHP version currently running, recent hosting changes and the compatibility requirements of affected components.

Where appropriate, reproduce the problem in staging and correct or replace incompatible code.

Do not blindly downgrade to an unsupported PHP version. That could introduce additional security and maintenance risks.

If PHP-FPM or required extensions are misconfigured, the hosting provider may need to assist.

Fix 5: Identify and Correct Faulty Custom PHP Code

Typical symptoms: The website crashes immediately after someone edits functions.php, installs a custom snippet or deploys new code.

A small PHP mistake can interrupt WordPress execution.

Common causes include missing syntax, duplicate function declarations, unavailable classes, incorrect arguments and incomplete deployments.

Check the latest fatal error entry for the relevant filename, line number and stack trace.

If the issue began after a specific change, compare the affected code with its previous working version.

Where version control or a verified backup is available, a controlled rollback of the change may be appropriate.

Avoid copying unverified PHP fixes from unrelated tutorials.

The file mentioned in an error may only be where the failure became visible, so complex issues often require a developer to investigate the complete execution path.

Fix 6: Investigate PHP Memory Limit Exhaustion

Typical symptoms: WordPress crashes during imports, page editing, plugin operations or other resource-intensive tasks.

An error log may contain:

Allowed memory size exhausted

This indicates that a PHP process attempted to use more memory than its configured limit.

Possible causes include resource-heavy extensions, inefficient database operations, large imports or faulty code repeatedly consuming memory.

Inspect the memory limit configured in PHP, the relevant WordPress memory settings and the hosting account's resource restrictions.

Identify which operation was running when the failure occurred.

A carefully assessed memory increase may help where legitimate workloads require more capacity.

However, increasing the PHP memory limit does not repair inefficient or defective code.

Avoid unlimited memory settings or arbitrary increases.

If the problem continues, a developer may need to optimise the operation while the hosting provider checks resource availability.

Fix 7: Repair Incomplete WordPress Updates or Damaged Files

Typical symptoms: The website breaks during or immediately after a WordPress core, plugin or theme update.

Interrupted updates can leave files missing, partially replaced or inconsistent with the installed application version.

Check the update history, relevant logs and the versions of affected components.

Where evidence points to damaged WordPress files, follow the official WordPress upgrading instructions.

Use trusted installation packages and preserve the current website configuration.

Never indiscriminately delete or overwrite wp-content or wp-config.php.

Those locations can contain essential themes, plugins, uploaded content and database connection settings.

For complex installations, a developer should repair the affected files using a verified backup or known-good release, then test the update process before repeating it on the live website.

Fix 8: Review Hosting, Server Configuration and File Permissions

Typical symptoms: Errors begin after a hosting migration, server upgrade or infrastructure change, even though no normal WordPress plugin was updated.

Potential causes include PHP-FPM failures, missing extensions, incorrect file ownership, insufficient disk space or hosting resource restrictions.

Check server logs and hosting notifications for relevant errors.

Determine whether the issue is genuinely a WordPress PHP fatal error or another problem, such as an HTTP 403 response, HTTP 500 response or database connection failure.

If the logs indicate a permissions problem, ask the hosting provider to confirm suitable ownership and access settings.

Never apply permission 777 broadly as a standard solution. This can create security vulnerabilities.

The correct settings depend on how the hosting environment operates.

For server-wide failures, resource restrictions and PHP configuration problems, hosting support is often the appropriate first contact.

Fix 9: Restore a Verified Backup When Targeted Repairs Are Insufficient

Typical symptoms: The website contains extensive file damage, multiple failed changes or an update that cannot be safely reversed.

A backup may provide a reliable recovery point, but restoration must be planned.

Before proceeding, confirm:

  • The backup contains the necessary files and database.
  • It was created when the website was functioning correctly.
  • The restoration method is supported by the hosting environment.
  • Recent orders, enquiries, bookings and account changes have been preserved.
  • The restored website can be tested properly.

A full database rollback may remove newer customer transactions or information.

For busy WooCommerce stores, consider whether a selective restoration of affected files is possible without overwriting current business records.

After restoration, investigate the original failure before repeating the operation that caused it.

A successful restore is not a substitute for understanding why the website broke.

How to Read WordPress Error Logs Safely

Error logs can help identify the precise PHP failure responsible for a critical error.

Useful information includes the error timestamp, affected file, line number and stack trace.

WordPress supports three important debugging constants:

  • WP_DEBUG enables WordPress debugging behaviour.
  • WP_DEBUG_LOG enables logging when debugging is active.
  • WP_DEBUG_DISPLAY controls whether debugging messages are displayed on pages.

For example, the official WordPress debugging documentation demonstrates these settings:

define( 'WP_DEBUG', true );

define( 'WP_DEBUG_LOG', true );

define( 'WP_DEBUG_DISPLAY', false );

These belong in wp-config.php before the WordPress configuration completion comment, with existing definitions handled correctly.

The standard log location is wp-content/debug.log when logging uses its default path.

Use a staging environment whenever possible.

If temporary live debugging is unavoidable, a qualified administrator should ensure that error details are not shown publicly and that log files cannot be downloaded by unauthorised visitors.

Logs may contain sensitive paths or application information.

After investigating, restore the site's intended production debugging configuration and securely remove unnecessary diagnostic records.

Remember that an error pointing to a particular file does not always prove that file originally caused the problem.

How Can You Fix a WordPress Critical Error Without wp-admin?

A critical error may prevent access to the WordPress dashboard entirely.

In that situation, recovery options include the hosting control panel, secure file manager, SFTP, PHP server logs and WordPress Recovery Mode.

WP-CLI may also be available to qualified administrators.

Begin by obtaining the most recent relevant fatal error and checking which component it identifies.

Then isolate or repair that component using the least disruptive method.

A website with a working front end but broken administrator dashboard may require a different investigation from a site where all public pages fail.

Avoid using insecure FTP, editing unfamiliar configuration files or executing destructive commands without a verified backup.

If hosting access or technical expertise is unavailable, request help before attempting potentially irreversible changes.

How to Test Your Website After Fixing the Critical Error

Removing the critical error message does not necessarily mean the website is fully working.

Complete these checks:

  1. Open the homepage and important service pages.
  2. Sign in to WordPress and confirm dashboard access.
  3. Test the mobile version and navigation.
  4. Submit a test enquiry and confirm its delivery.
  5. Verify appointment booking functionality where applicable.
  6. Test WooCommerce checkout using a safe test-payment method.
  7. Confirm important payment, CRM and third-party integrations.
  8. Check plugin-dependent features and theme functionality.
  9. Review error logs for recurring fatal errors.

Test the website outside any active Recovery Mode session.

A functioning homepage alone cannot confirm that customers can complete important actions.

Can a WordPress Critical Error Affect SEO and Customer Enquiries?

Yes. A critical error can prevent customers from viewing services, submitting forms, booking appointments or completing purchases.

If search engines repeatedly encounter server errors, crawling may slow down and prolonged problems can affect indexing.

However, a brief website interruption does not automatically result in a Google penalty or permanent ranking decline.

The actual impact depends on the affected URLs, server responses, duration and subsequent crawling.

After recovery, check important pages using Google Search Console and review any relevant server errors.

Businesses needing broader search visibility assistance can also explore Search Engine Optimisation services.

How to Prevent WordPress Critical Errors in the Future

Prevention starts with controlled website maintenance.

Maintain current backups, test restoration procedures and keep WordPress core, plugins and themes appropriately updated.

Check PHP compatibility before upgrades, particularly when using custom functionality or older extensions.

Use a staging environment to test significant changes and version control for custom code.

Monitor website availability, error logs and hosting resources.

Remove abandoned extensions only after evaluating their dependencies.

Automatic updates are useful, but they cannot guarantee that every plugin, theme and integration will remain compatible.

Important Considerations for UK Businesses

A critical error can affect different businesses in different ways.

A professional services company may lose enquiry opportunities, while a clinic could experience booking failures. An online retailer may lose checkout functionality.

During prolonged outages, businesses may need an alternative customer contact channel.

Backups, database exports, hosting credentials and error logs should be handled securely.

UK businesses should follow applicable data protection requirements when dealing with customer information.

A critical WordPress error does not automatically mean the website has been hacked or that a personal data breach has occurred.

Where there is actual evidence of compromised personal information, the circumstances should be assessed separately under appropriate Information Commissioner's Office guidance.

When Should You Hire a WordPress Developer?

Not every critical error requires paid professional assistance. Some clearly identified plugin issues can be resolved safely through supported updates or administrator tools.

Professional support becomes more relevant when:

  • Recovery Mode and wp-admin are unavailable.
  • The error keeps returning.
  • Custom PHP code or complex integrations are involved.
  • WooCommerce, bookings or customer transactions are affected.
  • Hosting support cannot identify the application-level issue.
  • Restoring a backup could overwrite important business information.

Provide the developer with the affected URL, incident time, recent changes, relevant error details and backup availability.

Do not send passwords or private hosting credentials through ordinary unsecured email.

Is a WordPress Critical Error Preventing Customers From Using Your Website?

A broken WordPress website may require more than restarting a plugin or restoring an old backup.

Identifying the underlying error helps reduce the risk of further disruption and protects important website functionality.

XCONS Solutions Ltd, a digital agency based in Ilford, East London, works with UK businesses on WordPress development, technical configuration and related website requirements.

If your website has recurring PHP errors, compatibility issues or complex integration problems, explore our WordPress Development services or contact the XCONS team to discuss your requirements.

For online stores, our WooCommerce Development services may also be relevant.

Share This :