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
Multiple Start Dates and Prices on creating a new event / new topic | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium Multiple Start Dates and Prices on creating a new event / new topic

Multiple Start Dates and Prices on creating a new event / new topic

Posted: September 7, 2012 at 2:09 pm

Viewing 2 reply threads


Cindi Landreth

September 7, 2012 at 2:09 pm

I have same problem that original topic outlined. I create a new event and it has multiple start times and prices. We just want it to default to one start time and one price.

It is far too much work for admin user to delete all, which does not work. I have to go into database and delete all of the start times, except one, manually.

Why does it create all of these start times. An event should only have on start time and one price.

What is the solution to have as a default only one start time and one price created on a new event?


Cindi Landreth

September 9, 2012 at 9:19 am

Fixed problem. For some reason, there were multiple records for wp_events_start_end and wp_events_prices where event_id = 0.

By deleting all of the unnecessary records, only leaving one, on add new event, only one start time and price widget is visible.


Dean

  • Support Staff

September 10, 2012 at 12:35 am

Glad you got it resolved, and thanks for posting your solution!

Viewing 2 reply threads

The support post ‘Multiple Start Dates and Prices on creating a new event / new topic’ 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.

Event Espresso - Staging Server