# Plugin could not be activated because it triggered a fatal error

**URL:** <https://meta.discourse.org/t/plugin-could-not-be-activated-because-it-triggered-a-fatal-error/52922>\
**Category:** WordPress\
**Created:** [November 15, 2016, 2:40pm UTC](https://meta.discourse.org/t/plugin-could-not-be-activated-because-it-triggered-a-fatal-error/52922 "2016-11-15T14:40:35Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![benword](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/benword/32/493782_2.png) [@benword](https://meta.discourse.org/u/benword)\
**Post date:** [November 28, 2016, 4:43am UTC](https://meta.discourse.org/t/plugin-could-not-be-activated-because-it-triggered-a-fatal-error/52922/16 "2016-11-28T04:43:16Z")

</div>

> [@cpradio](#):
>
> Isn’t PHP 5.3 EOL? Might be wiser to have the user upgrade their PHP so they are still getting security patches.

This is the best solution. Even if it’s a simple change to allow support for PHP 5.3, it’s a really bad idea to encourage any usage of it whatsoever.

PHP 5.3 has been unsupported for over 2 years. PHP 5.5 is EOL. PHP 5.6 support ends in 1 month.

---

_[View the full topic](https://meta.discourse.org/t/plugin-could-not-be-activated-because-it-triggered-a-fatal-error/52922)._