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 Limit number of attendees per price level | Event Espresso - Staging Server
Hi guys I have an event that has three different seating levels: Front Row, General, and Standing Room. I know I can create the different ticket costs, but I don’t see a way to limit the sale of those tickets by level. That is, I have 24 Front Row tickets, 76 General tickets, and 20 standing room tickets, which makes my total ticket sales potentially 120 tickets, but I can’t sell more than 24 front row tickets. Obviously, I don’t want to set up three different events, each with it’s own ticket limit; the bookkeeping trying to integrate the attendee lists would be nuts. This seems like a pretty basic function for a ticketing system, so I bet I’m just missing how to set it up.
This topic was modified 11 years, 10 months ago by Josh. Reason: added title
I gotta’ say, that’s a big lose. Many events have multiple levels of ticketing (for whatever reasons) and differing quantities for those different levels. I’d put this one at the top of your “to do” list.
You guys should check out http://www.BrownPaperTickets.com for functionality. They’re not perfect by any means, but they have a lot of good basic and advanced features that an event producer needs.
This is a feature that is in the plans to be included in a future release. It’s not something that will make it into the 4.0 release, but I’ll add your above comments to the ticket so the dev team is aware of your request.
Viewing 3 reply threads
The support post ‘Limit number of attendees per price level’ 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.