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 Attendee Limit - One event with 2 Show time | Event Espresso - Staging Server
I have created one event with 2 Event times.
e.g Event A on 30th July and Event times are 6PM and 9PM
For Event A I have configured the Attendee Limit as 200.
Does this mean the total limit is 200 ? ( 6PM event has 200 and 9PM event has 200 )
If you turn on quantity limits for time slots then you should control the seating limit with the time slot quantity. Each time slot quantity should be independent of each other (I haven’t personally confirmed that). But if you add a quantity to the Event Options field then that seating limit will override the time slot limit.
Thanks Garth – In which screen/page, I can configure the below ? ie configure Qty for time slots
>If you turn on quantity limits for time slots then you should control the seating limit with the time slot quantity.
The setting Garth referred to is under Event Espresso -> General Settings -> Optional Event Settings.
‘Use registration limits on time slots?’ set this to Yes.
You will then see a ‘Qty’ field under each time slot.
Hope this helps.
Viewing 3 reply threads
The support post ‘Attendee Limit – One event with 2 Show time’ 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.