Black FridayCyber Monday 2026
13Days
14Hrs
16Mins
31Secs
Flat20% OFF

Our biggest sale of the year20% off the first payment on all maintenance plans. Code BF2026

Grab the deal
WordPress

“Plugin Could Not Be Activated Because It Triggered a Fatal Error”: Fixes

WordPress tests a plugin before activating it and stops if it fails. Learn how to read the error, check PHP and WordPress requirements and fix the cause.

wpallsolution 7 min read

When WordPress says “Plugin could not be activated because it triggered a fatal error”, it ran the plugin’s code in a safe test, hit a PHP fatal error and stopped before the plugin could take down your site. That is good news: the plugin is not active, so your site should still work. The message usually carries the real PHP error underneath, which tells you what is wrong. This guide shows how to read it and how to fix the usual causes: version requirements, a conflict with another plugin, a damaged copy of the plugin, or server limits.

Quick answer

Read the error text shown below the message: it names a file, a line and what failed. If it says your PHP or WordPress version is too old, update them or choose a compatible plugin version. If it says a function or class already exists, another plugin (or a second copy of the same one) is in conflict. If the file looks damaged, delete the plugin folder and reinstall it from the official source. If it mentions memory or a missing function from a PHP extension, check your server. Keep a backup before you change anything.

How this guide was prepared: it is research-based. We read the WordPress source code listed under Sources, checked on October 23, 2026. We did not test your plugin or host, and the exact fix depends on the error text shown on your site.

What WordPress is doing

When you activate a plugin, WordPress loads it in a sandbox so that a fatal error does not break the whole site. In the WordPress code, a failed test produces the message “Plugin could not be activated because it triggered a fatal error.”, followed by the error output. Before that, WordPress can also check the plugin’s declared requirements: its code produces messages such as “Current PHP version (…) does not meet minimum requirements for … The plugin requires PHP …” or the same for the WordPress version, when your versions are lower than the plugin says it needs. These are different messages with different fixes, so read which one you have.

The decision tree: why did activation fail?

Flowchart for the WordPress message plugin could not be activated because it triggered a fatal error: five questions about the PHP error text, version requirements, duplicate functions, damaged files and server resources
Five questions point to why the plugin failed.
  1. A PHP error shown below the message? Read the file and error first (Step 1).
  2. It mentions a PHP or WordPress version? Compare with the plugin’s requirements (Step 2).
  3. A function or class already exists? Look for a duplicate or conflict (Step 3).
  4. Download or folder damaged? Reinstall from the official source (Step 4).
  5. Memory or a missing extension? Check the server (Step 5).

Symptoms and likely causes

What you seeLikely causeStart with
“The plugin requires PHP …” or “requires WordPress …”Your versions are older than the plugin allowsStep 2
“Cannot redeclare function …” or “Cannot declare class …”Two plugins (or two copies) define the same nameStep 3
“Call to undefined function …” for a PHP extension functionA required PHP extension is missingStep 5
“Allowed memory size … exhausted”Not enough memory for the plugin to loadStep 5
Parse error or unexpected end of fileA damaged or incomplete plugin fileStep 4

5 steps to fix “Plugin could not be activated because it triggered a fatal error”

Step 1: Read the PHP error under the message

Copy the whole message. The error line usually has a type (Parse error, Fatal error), a text, a file path and a line number. The folder name in the path tells you which plugin or theme file caused it, which may be a different plugin from the one you were activating. If no detail appears, turn on logging and read the file; see how to read the WordPress debug log safely.

Step 2: Check the version requirements

Compare your PHP and WordPress versions (Tools → Site Health → Info) with what the plugin’s page and readme say it needs. If your PHP is too old, ask your host to upgrade it after checking that your other plugins and theme support the newer version; if the plugin is too new for your WordPress, update WordPress safely or use an older plugin release that your versions support. Our guide to updating WordPress plugins safely describes a careful routine.

Step 3: Look for conflicts and duplicates

If the error says a function or class already exists, another active plugin or the theme declares the same name. A common case is a free and a pro version of the same plugin, or a plugin installed twice under different folder names. Deactivate the older copy first. If you cannot tell which plugins conflict, follow how to find the plugin that broke your site and WordPress plugin conflict.

Step 4: Reinstall a clean copy

A broken download, an interrupted update or a zip that unpacked into a folder inside a folder can leave files incomplete. Delete the plugin folder in wp-content/plugins (over SFTP or your host’s file manager if the dashboard cannot), then download the plugin again from its official source and install it. Keep your settings in mind: deleting a plugin’s folder does not remove its settings from the database, but take a backup first.

Step 5: Check server resources and PHP extensions

If the error mentions memory, see Allowed memory size exhausted. If it says a function does not exist and the function belongs to a PHP extension (such as image, string or XML handling), ask your host to enable the extension for your PHP version. Also check that the plugin supports the PHP version you run, since a plugin written for an older PHP can break on a newer one.

Version and hosting differences

  • Plugins can declare minimum PHP and WordPress versions; WordPress checks them before activation.
  • Managed hosts may run a different PHP version per site, so check yours in the hosting panel.
  • Multisite activates plugins per site or for the whole network, so errors can differ.

How to verify the fix

  • The plugin activates and its settings page opens.
  • The front end and the admin still work.
  • The error log shows no new fatal errors, and Site Health has no new critical issue.

How to prevent it from happening again

  • Check a plugin’s requirements and last update before you install it.
  • Test new plugins on a staging copy.
  • Remove plugins you no longer use, and keep PHP supported.
  • Keep it in your maintenance routine.

Frequently asked questions

Is my site broken?

Usually not. WordPress stopped the activation so the plugin would not take the site down.

Can I still use the plugin?

Often yes, once you fix the cause, for example by updating PHP, removing a conflicting plugin or reinstalling.

Why does it name another plugin?

The error may be in a file from a different plugin or the theme that the new plugin interacts with.

Should I contact the developer?

Yes, with the exact message, your PHP and WordPress versions and your other active plugins.

What to do next

Read the error, check the requirements and remove conflicts. If the plugin is business-critical and still fails, wpallsolution offers plugin support and an emergency WordPress fix. We cannot promise a result without seeing the error on your site.

Sources and official documentation

Keep reading

More guides

Need a hand with this?

Tell us what is happening. We reply with honest next steps.

Talk to us