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 early bird special by ticket quantity instead of date | Event Espresso - Staging Server
Hi, am trying to setup so that the first 1500 tickets have a special gift after which the next 2500 are normal tickets.
This was done previously with other system when ticket type a is sold out ticket type b is up for sale. As the ticket description is different, the staff at the event can identify them easily.
Event Espresso is not able to limit individual ticket type numbers within a single event right now.
The best way to do it would be to have two separate events with the max attendee count limited. Then you could use Multiple Event Register or a custom Event List to display them and users can choose if they want the gift or not.
You could use some jquery to hide the secondary non gift event until the attendee count for the first has hit zero.
One other way to do it would be to use the Waiting list functionality, when event A fills up, the user is directed to sign up at event B.
Pros – automated, different ticket names as they are different events.
Problems with this is that it would require some customisation of the templates as currently it would show this message http://d.pr/i/eqwT
Thanks for taking the time to leave this valuable feedback. I’ve registered your suggestion and we will keep it in mind for future features and updates!
Viewing 3 reply threads
The support post ‘early bird special by ticket quantity instead of date’ 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.