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
512 Start End Times | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Lite › 512 Start End Times

512 Start End Times

Posted: December 12, 2013 at 8:20 am

Viewing 1 reply thread


christopher mann

December 12, 2013 at 8:20 am

New events are automatically created with 512 “Start/End” fields. Without deleting them all, the event cannot be created (returns to blank page). This essentially makes Event Espresso non-functional, a great pity!

*WordPress Version: 3.7.1
*Event Espresso Version: 3.1.35.L
*Website: ctnsp.dodlive.mil/
*Installed Plugins:
-All In One SEO Pack 2.0.4
-Breadcrumb NavXT 4.4.0
-Contact Form 7 3.5.3
-Disqus Comment System 2.74,
-Event Espresso Lite – 3.1.35.L
-Flexi Pages Widget by Srini G version 1.6.13
-Flickr Gallery version 1.5.2
-IFrame Widget 4.1
-Custom CSS by CTLT 2.0.3
-Post Thumbnail Editor 2.2.1
-Specific CSS/JS for Posts and Pages 1.0
-WP-PageNavi 2.8


Josh

December 12, 2013 at 10:52 am

Hi Christopher,

Have you tried creating a new event with all of those plugins (except Event Espresso, of course) deactivated?
Viewing 1 reply thread

The support post ‘512 Start End Times’ 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.

Community-based support for the free version of Event Espresso.

Status: closed

Updated by Josh 11 years, 1 month ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server