Title: Parse error
Last modified: August 22, 2016

---

# Parse error

 *  [ironivan89](https://wordpress.org/support/users/ironivan89/)
 * (@ironivan89)
 * [11 years, 2 months ago](https://wordpress.org/support/topic/parse-error-316/)
 * Parse error: syntax error, unexpected end of file in D:\xampp\htdocs\clubix\wp-
   content\plugins\golden-ticket\options.php on line 439 when I try to enter in 
   golden ticket menu
 * FIND: change some <? with <?php in options.php
 * [https://wordpress.org/plugins/golden-ticket/](https://wordpress.org/plugins/golden-ticket/)

Viewing 2 replies - 1 through 2 (of 2 total)

 *  Plugin Author [The Plugin Factory](https://wordpress.org/support/users/the-plugin-factory/)
 * (@the-plugin-factory)
 * [11 years, 2 months ago](https://wordpress.org/support/topic/parse-error-316/#post-5949110)
 * Yes, thank you for the report. On the next release, I’ll fix the opening PHP 
   tags to not be short tags like that.
 *  Plugin Author [The Plugin Factory](https://wordpress.org/support/users/the-plugin-factory/)
 * (@the-plugin-factory)
 * [11 years, 2 months ago](https://wordpress.org/support/topic/parse-error-316/#post-5949301)
 * Released a new version

Viewing 2 replies - 1 through 2 (of 2 total)

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

 * ![](https://s.w.org/plugins/geopattern-icon/golden-ticket_b6ae9e.svg)
 * [Golden Ticket](https://wordpress.org/plugins/golden-ticket/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/golden-ticket/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/golden-ticket/)
 * [Active Topics](https://wordpress.org/support/plugin/golden-ticket/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/golden-ticket/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/golden-ticket/reviews/)

 * 2 replies
 * 2 participants
 * Last reply from: [The Plugin Factory](https://wordpress.org/support/users/the-plugin-factory/)
 * Last activity: [11 years, 2 months ago](https://wordpress.org/support/topic/parse-error-316/#post-5949301)
 * Status: not resolved