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 Tickets not deducting from Time Slots when attendees added | Event Espresso - Staging Server
I have just tested this to see if I could replicate and using EE 3.1.29.1.P I could not recreate. No matter which time slot I chose, or however many tickets it correctly deducted the number of tickets.
Is your event espresso and appropriate addons up to date?
After testing repeatedly – no matter how many tickets you choose & purchase… it still only deducts 1 from “available spaces” …
I have to say that Event Espresso has been really frustrating. not as advertised …with multiple events … really buggy.
The only easy set-up is having a one -out event date without multiple time slots.
At this time the time slot quantity feature is experimental and can only support group registrations if the option is set to require information for the additional attendees. Registration forms that use the ticket quantity selector will get counted as a single registration for that time slot.
I’m going to bump the ticket in our issue tracker to see if we can get one of the dev’s to investigate further.
Viewing 3 reply threads
The support post ‘Tickets not deducting from Time Slots when attendees added’ 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.