Title: Parse error when activating plugin
Last modified: February 22, 2018

---

# Parse error when activating plugin

 *  [cauemeneghelli](https://wordpress.org/support/users/cauemeneghelli/)
 * (@cauemeneghelli)
 * [8 years, 3 months ago](https://wordpress.org/support/topic/parse-error-when-activating-plugin-3/)
 * Hello Aerin,
    When trying to activated the plugin I get the following error:.
 * “Parse error: syntax error, unexpected ‘[‘ in /home/rjlengnew/public_html/wp-
   content/plugins/quick-paypal-payments/quick-paypal-payments.php on line 2402”
 * Any thoughts on what could be causing it?
 * This is my wordpress details:
    WordPress 4.9.4 running Virtue theme. Running 
   PHP version: 5.3.29
 * Thank you.

Viewing 1 replies (of 1 total)

 *  [Graham](https://wordpress.org/support/users/aerin/)
 * (@aerin)
 * [8 years, 3 months ago](https://wordpress.org/support/topic/parse-error-when-activating-plugin-3/#post-10014633)
 * You are running an old and unsupported version of PHP. The end of life for 5.3
   was back in 2014.
 * Wordpress recommends you use version 7. If you upgrade the plugin will work.

Viewing 1 replies (of 1 total)

The topic ‘Parse error when activating plugin’ is closed to new replies.

 * ![](https://ps.w.org/quick-paypal-payments/assets/icon-128x128.png?rev=3412386)
 * [Quick Paypal Payments](https://wordpress.org/plugins/quick-paypal-payments/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/quick-paypal-payments/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/quick-paypal-payments/)
 * [Active Topics](https://wordpress.org/support/plugin/quick-paypal-payments/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/quick-paypal-payments/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/quick-paypal-payments/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [Graham](https://wordpress.org/support/users/aerin/)
 * Last activity: [8 years, 3 months ago](https://wordpress.org/support/topic/parse-error-when-activating-plugin-3/#post-10014633)
 * Status: not resolved