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 maximum qty | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Group maximum qty

Group maximum qty

Posted: October 22, 2013 at 4:32 pm

Viewing 1 reply thread


Eve

October 22, 2013 at 4:32 pm

I am using multi-event registration and need to limit the qty of each ticket type to 10. I have tried using the group qty but noticed the restriction is on 10 of any type of ticket. So you can’t buy 10 X Ticket A and 10 x Ticket B, only 10 x Ticket A OR B OR combination of both.

Is there any easy way of changing it so the restriction is placed on the individual ticket options under the event?

I hope this makes sense.


Garth

  • Support Staff

    •

October 22, 2013 at 8:03 pm

Hi Eve,

Currently the quantity restrictions are event-based, not ticket based. So if you only want to allow the purchase of a certain ticket, then you’ll have to make an event with only one ticket (thus multiple events of the same type but a different ticket).

With the Multiple Event Registration addon (http://staging.eventespresso.com/product/espresso-multiple/) they can add multiple events (tickets) to their cart and you can limit the quantities that way. We’ve got a great fix for that announced on our blog: http://staging.eventespresso.com/2013/09/event-espresso-4-feature-showcase-ticket-quantity-uses-min-and-max/
Viewing 1 reply thread

The support post ‘Group maximum qty’ 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.

The original Forum description...

Status: closed

Updated by Garth 11 years, 3 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server