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
Attendee Limit for each Price | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Attendee Limit for each Price

Attendee Limit for each Price

Posted: February 11, 2013 at 6:53 am

Viewing 1 reply thread


Richard Leino

February 11, 2013 at 6:53 am

Is this going anywhere: http://staging.eventespresso.com/forums/2011/08/attendee-limit-for-each-price-type/

I hate to resurrect an old thread but I can’t vote on an idea that severely limits my ability. My only option right now is to create three events for the same event to limit certain attendee types from buying all the slots.


Jonathan Wilson

  • Support Staff

    •

February 11, 2013 at 1:38 pm

Hello Richard,

Thank you for bringing this back up. Our developers have revisited this in the last few days and they are working on resolving the issue. I don’t have an ETA as of now, but it is being worked on. Feel free to check on this at anytime.
Viewing 1 reply thread

The support post ‘Attendee Limit for each Price’ 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 Jonathan Wilson 11 years, 11 months ago ago

Topic Tags

Tagged: 

Notifications

This topic is: not resolved
Event Espresso - Staging Server