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
Group Attendees not reducing attendees | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium Group Attendees not reducing attendees

Group Attendees not reducing attendees

Posted: November 24, 2013 at 10:15 am

Viewing 3 reply threads


Alan Coyne

November 24, 2013 at 10:15 am

Hi,
I’ve setup an event with different time slots and have a max attendees of 4 on each time slot.

If I purchase 3 tickets, the number of spaces available only reduces by 1. Is there a way to reduce the number of attendees by the number of tickets purchased?

Version 3.1.3
Thanks
Alan


Dean

  • Support Staff

November 25, 2013 at 1:45 am

Hi Alan,

This is something we are aware of but unfortunately there is no fix in place for it.

According to the developers database structure in 3.1 does not support group bookings for time slots.

As such it is quite unlikely a fix will be added to 3.1.

Going forward version 4.0 uses a different database structure (4.0 is different to 3.1 on many levels) and can support a more flexible ticketing structure.


Alan Coyne

November 25, 2013 at 2:20 am

Hi Dean,

When roughly would you expect version 4 to be ready?

thanks

Alan


Dean

  • Support Staff

November 25, 2013 at 3:04 am

Hi Alan,

Not firm release date as yet, but we are looking to get the first Alpha version out ASAP, it is our number one priority.

Viewing 3 reply threads

The support post ‘Group Attendees not reducing attendees’ 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