Title: Parse Error &#8211; Website is down!!
Last modified: August 22, 2016

---

# Parse Error – Website is down!!

 *  Resolved [gralmy](https://wordpress.org/support/users/gralmy/)
 * (@gralmy)
 * [11 years, 8 months ago](https://wordpress.org/support/topic/parse-error-website-is-down/)
 * Parse error: syntax error, unexpected T_VARIABLE in /home/content/30/11968430/
   html/songbirdcollectibles/wp-content/themes/eventbrite/plugins/keyring/includes/
   services/core/template.php on line 1
 * is what comes up when I try to access the site. this plugin must have come with
   the theme, I don’t even know what it’s used for. the theme is Eventbrite.
 * Help!
 * thanks!
 * [https://wordpress.org/plugins/keyring/](https://wordpress.org/plugins/keyring/)

Viewing 1 replies (of 1 total)

 *  Plugin Author [Beau Lebens](https://wordpress.org/support/users/beaulebens/)
 * (@beaulebens)
 * [11 years, 7 months ago](https://wordpress.org/support/topic/parse-error-website-is-down/#post-5338092)
 * Keyring is used to handle authentication with remote services (e.g. Eventbrite),
   but this error appears to be in the theme you’re using, not within Keyring itself.
   Please contact the author of the theme to get it fixed.

Viewing 1 replies (of 1 total)

The topic ‘Parse Error – Website is down!!’ is closed to new replies.

 * ![](https://ps.w.org/keyring/assets/icon-256x256.png?rev=1824013)
 * [Keyring](https://wordpress.org/plugins/keyring/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/keyring/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/keyring/)
 * [Active Topics](https://wordpress.org/support/plugin/keyring/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/keyring/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/keyring/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [Beau Lebens](https://wordpress.org/support/users/beaulebens/)
 * Last activity: [11 years, 7 months ago](https://wordpress.org/support/topic/parse-error-website-is-down/#post-5338092)
 * Status: resolved