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
Capping registration of different price types | Event Espresso - Staging Server

Support

Home › Forums › Pre-Sales › Capping registration of different price types

Capping registration of different price types

Posted: February 11, 2013 at 11:44 am

Viewing 1 reply thread


Jeffrey

February 11, 2013 at 11:44 am

I’m looking to set a limit on how many attendees can register per price type. For example, there will be multiple lodging options with a specific limit on availability of each specific room type. Is this something that can be done. If not, is there some sort of work around that you know of?


Josh

February 11, 2013 at 12:19 pm

Hi Jeffrey,

At this time, price types cannot be capped. The workaround is to create an event for each price type, then you can cap registration limits.
Viewing 1 reply thread

The support post ‘Capping registration of different price types’ 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.

Status: closed

Updated by Josh 11 years, 11 months ago ago

Topic Tags

Tagged: , ,

Notifications

This topic is: not resolved
Event Espresso - Staging Server