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
recurring events, multiple daily timeslots | Event Espresso - Staging Server

Support

Home › Forums › Recurring Events Manager › recurring events, multiple daily timeslots

recurring events, multiple daily timeslots

Posted: February 11, 2013 at 5:28 am

Viewing 1 reply thread


Bjørn Tore Stig

February 11, 2013 at 5:28 am

Hi,

We have an installation where we have set up recurring events, there are three dates. In addition, we have also multiple timeslots, there are 2 set up.
Now, when we list these events using event_list.php in uploads, there should be 6 lines – 3 days with 2 timeslots each. We only get 3 lines. First line is first date with last timeslot, the next two lines are the remaining days, both with first timeslot.
To me it looks like the SQL doesn’t do what it should…
Any ideas?


Josh

February 11, 2013 at 8:44 pm

Hi Bjørn,

The event list SQL isn’t querying all the event times, so it’s only going to display one time for each event in the list. If you want each event time to show up as an event, I can recommend creating one event for each time. They will show up as 6 lines this way.
Viewing 1 reply thread

The support post ‘recurring events, multiple daily timeslots’ 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.

Status: closed

Updated by Josh 11 years, 11 months ago ago

Topic Tags

Tagged: 

Notifications

This topic is: not resolved
Event Espresso - Staging Server