# 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:** [Novembre 15, 2016, 2:40 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:** 13

<div class="post-metadata">

**Author:** ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)\
**Post date:** [Novembre 17, 2016, 5:30 UTC](https://meta.discourse.org/t/plugin-could-not-be-activated-because-it-triggered-a-fatal-error/52922/13 "2016-11-17T05:30:02Z")

</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.

Assuming that the packages being used are those provided by the OS vendor, that version of PHP _will_ get security updates, based on backported patches of security vulnerabilities provided for later releases.

---

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