# 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:** [15 Noviembre, 2016 14: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:** 8

<div class="post-metadata">

**Author:** ![cpradio](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/cpradio/32/4970_2.png) [@cpradio](https://meta.discourse.org/u/cpradio)\
**Post date:** [15 Noviembre, 2016 21:56 UTC](https://meta.discourse.org/t/plugin-could-not-be-activated-because-it-triggered-a-fatal-error/52922/8 "2016-11-15T21:56:18Z")

</div>

Isn’t PHP 5.3 EOL? Might be wiser to have the user upgrade their PHP so they are still getting security patches.

---

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