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 Two Pricing Choices General & VIP, need to stop VIP | Event Espresso - Staging Server
If I have been selling two different priced tickets for an event, General Admission and VIP, and I need to stop the VIP as I have sold the quota, can I just delete that price? It won’t stop the preciously purchased VIP tickets from working this weekend when they get scanned at the door this Saturday at the event right?
Really it should have been set up using the Multiple Event Registration so that the VIP would have been another event as such but the event would have closed down when the ticket quota got reached.
However you should be fine deleting the price as the info is stored in the database.
Yeah I didn’t realize that until after it was put into play… I’ll delete the extra price and see what happens, BUT it would seem that if you have the ability to have more than one price, you should be able to set time limits on the different prices instead of having to make a separate event… i don’t know, maybe it’s just as easy to make an additional event and not have the second prices. cheers.
It’s something we are looking at in 3.2 but that will be a while yet.
Viewing 3 reply threads
The support post ‘Two Pricing Choices General & VIP, need to stop VIP’ 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.