Title: Fatal Error When Activating Plugin
Last modified: April 24, 2017

---

# Fatal Error When Activating Plugin

 *  [phenn](https://wordpress.org/support/users/phenn/)
 * (@phenn)
 * [9 years, 1 month ago](https://wordpress.org/support/topic/fatal-error-when-activating-plugin-34/)
 * Good morning. I tried to install your plugin (current Moosend customer) and got
   the following.
 * Parse error: syntax error, unexpected ‘[‘ in /home/company/public_html/regroup/
   wp-content/plugins/moosend-email-marketing/vendor/react/promise/src/functions.
   php on line 15
 * Any ideas? Using latest WP install and latest Impreza theme.

Viewing 1 replies (of 1 total)

 *  Plugin Author [moosend](https://wordpress.org/support/users/moosend/)
 * (@moosend)
 * [8 years, 11 months ago](https://wordpress.org/support/topic/fatal-error-when-activating-plugin-34/#post-9204436)
 * Hi Phenn,
 * Apologies for the late reply. Somehow we missed this!
 * So we believe you may have an old version of PHP there. You neeed at least 5.4
   for our plugin. Can you confirm your version and get back to me?
 * Thanks

Viewing 1 replies (of 1 total)

The topic ‘Fatal Error When Activating Plugin’ is closed to new replies.

 * ![](https://ps.w.org/moosend-email-marketing/assets/icon-256x256.png?rev=1640707)
 * [Moosend Website Connector](https://wordpress.org/plugins/moosend-email-marketing/)
 * [Support Threads](https://wordpress.org/support/plugin/moosend-email-marketing/)
 * [Active Topics](https://wordpress.org/support/plugin/moosend-email-marketing/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/moosend-email-marketing/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/moosend-email-marketing/reviews/)

## Tags

 * [fatal error](https://wordpress.org/support/topic-tag/fatal-error/)

 * 1 reply
 * 2 participants
 * Last reply from: [moosend](https://wordpress.org/support/users/moosend/)
 * Last activity: [8 years, 11 months ago](https://wordpress.org/support/topic/fatal-error-when-activating-plugin-34/#post-9204436)
 * Status: not resolved