Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114 500 Internal Server Error while activating Event Espresso – Ticketing | Event Espresso - Staging Server
I have 500 Internal Server Error while activating Event Espresso – Ticketing
My WP version – 3.5.2
Event Espresso version 3.1.33.3.P
New installation
Installed plugins
Add Meta Tags by George Notaras version 2.1.1,
Contact Form 7 by Takayuki Miyoshi version 3.4.2,
Event Espresso – Calendar by Event Espresso version 2.0.6.1,
Event Espresso – Social Coupons by Seth Shoultes version 1.5.3.1,
Event Espresso – Multi Event Registration by Seth Shoultes version 1.0.4,
Event Espresso – Permissions by Event Espresso version 1.5.4.1,
Event Espresso – Recurring Events by Event Espresso version 1.1.7.1,
Event Espresso Requirements Check by Event Espresso version 0.9,
Event Espresso by Event Espresso version 3.1.33.3.P,
Google Map Shortcode by Alain Gonzalez version 3.1.2,
Google XML Sitemaps by Arne Brachhold version 3.2.9,
Google Analytics by Kevin Sylvestre version 1.0.5,
Theme Test Drive by Vladimir Prelovac version 2.8.4,
WP-Mail-SMTP by Callum Macdonald version 0.9.1,
WP-Memory-Usage by Alex Rabe version 1.2.1,
WSA Favicon by WebStartAvenue version 1.0
I don’t have registration page
Please let me know what to do
Thanks,
Ofir
This topic was modified 11 years, 6 months ago by Ofir Avidan.
You havent mentioned what version of Ticketing you have, but the latest version 2.0.10.1 should resolve the fatal error issue.
You can download it from your account page.
Viewing 1 reply thread
The support post ‘500 Internal Server Error while activating Event Espresso – Ticketing’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.