WordPress: Plugin could not be activated because it triggered a fatal error
Activating the plugin caused a PHP fatal error — usually PHP version incompatibility, a conflict with another plugin/theme, or missing PHP extensions.
Seen on:
WordPress
Meaning
WordPress catches the error during activation. Enable WP_DEBUG_LOG to see the real error in wp-content/debug.log (function redeclared, class not found, syntax error for your PHP version).
Common causes
- Plugin requires a newer/older PHP version
- Function/class name conflict with another plugin
- Missing PHP extension (intl, mbstring, sodium)
- Corrupted/incomplete upload
⚡ Quick fix
- Turn on WP_DEBUG_LOG and read wp-content/debug.log
- Check PHP version requirements
- Deactivate conflicting plugins and retry
Detailed fix by platform
WordPress
- php
// wp-config.php define('WP_DEBUG', true); define('WP_DEBUG_LOG', true); define('WP_DEBUG_DISPLAY', false);
How to diagnose
- Log — debug.log error
- PHP — Version vs requirements
- Conflicts — Other plugins
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- Allowed memory size exhausted PHP Fatal error: Allowed memory size of X bytes exhausted
- ArgumentCountError Fatal error: Uncaught ArgumentCountError: Too few arguments to function foo(), 1 passed and exactly 2 expected
- Call to member function on null Fatal error: Uncaught Error: Call to a member function x() on null
Most viewed in WordPress
Other ways to find it
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 7 Oct 2026