How to Troubleshoot and Fix WordPress Plugin Causing Critical Error After Activation

Learn how to safely recover your WordPress site when activating a plugin triggers a “There has been a critical error on this website” message, and how to prevent it in the future.

Overview

If you activate a plugin and suddenly see “There has been a critical error on this website” or a blank screen, it usually means that plugin is conflicting with your theme, another plugin, or your server limits.

This guide walks you through safely restoring access to your site, disabling the problem plugin, and preventing similar issues in the future.

Before You Start

• Have access to your hosting control panel (cPanel, Plesk, or similar) or FTP/SFTP credentials.
• Know the name of the plugin you just activated (or recently updated).
• Have your WordPress admin login ready in case you can still access the dashboard.

Step 1 – Confirm the Error Is Plugin-Related

Most of the time, the critical error appears immediately after activating or updating a plugin. Typical symptoms include:

• Front-end shows a white screen or the critical error message.
• Admin area (/wp-admin) is also inaccessible or partially broken.
• The issue started right after enabling or updating a specific plugin.

If You Receive a Recovery Mode Email

WordPress may send an email to your admin address with the subject line similar to “Your Site is Experiencing a Technical Issue.” This email often includes:

• A link to enter Recovery Mode.
• The name of the plugin causing the error.
• A short error message (e.g., fatal error in a specific file).

If you have this email, use the Recovery Mode link first (see Step 2A).

Step 2 – Disable the Problem Plugin

Your first goal is to turn off the plugin that triggered the error so the site can load again.

Step 2A – Disable via WordPress Recovery Mode (If Available)

1. Open the email from WordPress about the technical issue.
2. Click the Recovery Mode link in the email.
3. Log in with your usual WordPress admin credentials.
4. In the dashboard banner, review the list of plugins with issues.
5. Click Deactivate next to the plugin named in the error.

What You Should See: After deactivating the plugin, the error banner should disappear and your site’s front-end should load normally in another browser tab.

Step 2B – Disable via File Manager or FTP (If You Can’t Access Admin)

If Recovery Mode is not available or the admin area is completely down, disable the plugin at the file level.

Using Hosting File Manager

1. Log in to your hosting control panel (e.g., cPanel).
2. Open File Manager.
3. Navigate to your WordPress install directory, usually public_html or a subfolder.
4. Go to wp-content ? plugins.
5. Find the folder that matches the plugin name you just activated (for example, contact-form-7).
6. Rename the folder, for example from plugin-name to plugin-name-disabled.

Renaming the folder forces WordPress to deactivate the plugin.

Using FTP/SFTP

1. Connect to your site using an FTP/SFTP client (FileZilla, Cyberduck, etc.).
2. Browse to your WordPress root folder.
3. Open wp-content ? plugins.
4. Right-click the suspected plugin folder and choose Rename.
5. Add -disabled to the end of the folder name.

What You Should See: Refresh your website in a new browser tab. The critical error should be gone, and you should be able to log back into /wp-admin.

Step 3 – Confirm the Site Is Stable

Once the plugin is disabled and the site loads again, verify that everything is working as expected.

• Visit your homepage and a few key pages (e.g., Services, Contact).
• Log in to Dashboard ? Plugins ? Installed Plugins and confirm the plugin shows as inactive or missing.
• Check any critical functionality related to that plugin (forms, sliders, SEO, etc.).

Step 4 – Identify Why the Plugin Caused a Critical Error

Now that your site is back online, it’s time to understand the cause so you can decide whether to keep, replace, or remove the plugin.

4.1 – Check the Error Details (If Available)

If you still have the technical issue email from WordPress, look for:

• Plugin name – confirms the culprit.
• File path – often shows which plugin file failed.
• PHP error type – for example, Fatal error or Parse error.

4.2 – Enable Debugging Temporarily (Advanced but Helpful)

If you’re comfortable editing files, you can enable debugging to see more detailed error messages.

1. In File Manager or FTP, open your site root and locate wp-config.php.
2. Download a backup copy of the file first.
3. Open wp-config.php in a code editor.
4. Find the line that says define( 'WP_DEBUG', false ); and change it to:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

This logs errors to wp-content/debug.log without showing them to visitors.

Important: Turn debugging back off after you’re done by setting WP_DEBUG to false.

Step 5 – Decide What to Do with the Problem Plugin

Once you know which plugin caused the issue, choose a safe path forward.

Option A – Replace the Plugin

Recommended when:

• The plugin hasn’t been updated in a long time.
• It’s not essential, or there are well-supported alternatives.
• Your host or developer confirms it’s poorly coded or incompatible.

Steps:

1. From Dashboard ? Plugins ? Installed Plugins, click Delete on the problematic plugin.
2. Search for an alternative under Plugins ? Add New.
3. Install and activate the new plugin, then configure it carefully.

Option B – Reinstall a Fresh Copy

Sometimes a plugin file becomes corrupted during upload or update.

1. Delete the existing plugin from Dashboard ? Plugins (or remove its folder via File Manager).
2. Go to Plugins ? Add New and search for the same plugin.
3. Install and activate it again.

Tip: If the error returns immediately after reactivation, stop and consider replacing the plugin instead.

Option C – Keep the Plugin but Adjust Your Environment

In some cases, the plugin is fine but your server limits are too low (for example, memory limit or PHP version).

Discuss with your host or developer about:

• PHP version – Many plugins require PHP 7.4 or higher.
• Memory limit – Increasing WP_MEMORY_LIMIT can help heavy plugins.
• Conflicting plugins – Two plugins trying to do the same thing can clash.

Step 6 – Test Safely Before Reactivating

If you want to try the plugin again, do it in a controlled way.

6.1 – Use a Staging Site (Best Practice)

If your hosting provides staging:

1. Create a staging copy of your site from your hosting panel.
2. Log in to the staging site’s WordPress dashboard.
3. Install or activate the plugin on staging first.
4. Test all relevant pages and features thoroughly.

Only apply the change to the live site after confirming staging is stable.

6.2 – If You Must Test on the Live Site

• Take a full backup (files + database) via your host or a backup plugin.
• Ensure low-traffic timing (off-peak hours).
• Reactivate the plugin and immediately test key pages and forms.
• If the error reappears, disable the plugin again using Step 2.

What You Should See After Fixing

Once the issue is resolved, you should observe:

• No more “critical error” messages on the front-end or admin.
• Normal access to Dashboard ? Plugins.
• Only stable, active plugins listed; the problematic one is either inactive, removed, or replaced.
• All key site features (navigation, forms, checkout, etc.) working as expected.

How to Prevent Plugin-Related Critical Errors

To reduce the risk of this happening again, adopt these habits:

• Limit plugins – Only install what you truly need.
• Choose reputable plugins – Check ratings, active installs, and recent updates.
• Update regularly but carefully – Avoid updating many plugins at once on a busy live site.
• Use staging for major changes – Test new or complex plugins before live activation.
• Keep backups – Maintain automatic daily backups with your host or a backup tool.

When to Contact Compass Production or Your Developer

Reach out for professional help if:

• The site remains down even after disabling the suspected plugin.
• You’re not comfortable using File Manager or FTP.
• The error involves custom code or a mission-critical integration.
• You need guidance choosing a safe replacement plugin.

Providing your developer with the error email, any debug.log entries, and a list of recently changed plugins will help them resolve the issue faster.

Video