Title: Parse error: syntax error, unexpected
Last modified: August 31, 2016

---

# Parse error: syntax error, unexpected

 *  [seowizardindia](https://wordpress.org/support/users/seowizardindia/)
 * (@seowizardindia)
 * [10 years, 1 month ago](https://wordpress.org/support/topic/parse-error-syntax-error-unexpected-166/)
 * Parse error: syntax error, unexpected ‘[‘ in /home/content/58/9640958/html/wp-
   content/plugins/easy-paypal-events-tickets/includes/private_buttons_new.php on
   line 14
 * i got this error when i went to create a new event after completing the settings.
 * [https://wordpress.org/plugins/easy-paypal-events-tickets/](https://wordpress.org/plugins/easy-paypal-events-tickets/)

Viewing 1 replies (of 1 total)

 *  Plugin Author [Scott Paterson](https://wordpress.org/support/users/scottpaterson/)
 * (@scottpaterson)
 * [10 years, 1 month ago](https://wordpress.org/support/topic/parse-error-syntax-error-unexpected-166/#post-7301618)
 * Hi seowizardindia,
 * Hm, sorry about that. Let me look into this and I’ll get back to you.
 * Thanks,
    Scott

Viewing 1 replies (of 1 total)

The topic ‘Parse error: syntax error, unexpected’ is closed to new replies.

 * ![](https://ps.w.org/easy-paypal-events-tickets/assets/icon-256x256.png?rev=3095888)
 * [Easy PayPal Events & Tickets](https://wordpress.org/plugins/easy-paypal-events-tickets/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/easy-paypal-events-tickets/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/easy-paypal-events-tickets/)
 * [Active Topics](https://wordpress.org/support/plugin/easy-paypal-events-tickets/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/easy-paypal-events-tickets/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/easy-paypal-events-tickets/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [Scott Paterson](https://wordpress.org/support/users/scottpaterson/)
 * Last activity: [10 years, 1 month ago](https://wordpress.org/support/topic/parse-error-syntax-error-unexpected-166/#post-7301618)
 * Status: not resolved