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
Multiple Event Pricing question | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Lite › Multiple Event Pricing question

Multiple Event Pricing question

Posted: June 26, 2013 at 10:31 am

Viewing 1 reply thread


jomo

June 26, 2013 at 10:31 am

I have 3 different prices / levels for my tickets. One of them being VIP – and we want to cap these VIP sales  – Can i simply just delete this pricing option in my event, without effecting all of the previously purchased tickets?

Thanks!


Jonathan Wilson

  • Support Staff

    •

June 26, 2013 at 2:37 pm

Hi Jomo,

Yes. You can do that. It should not cause any problems. The user should remain in the database. I just tested this on one of my test servers. Let us know if you have any issues.
Viewing 1 reply thread

The support post ‘Multiple Event Pricing question’ 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.

Community-based support for the free version of Event Espresso.

Status: closed

Updated by Jonathan Wilson 11 years, 6 months ago ago

Topic Tags

Tagged: 

Notifications

This topic is: not resolved
Event Espresso - Staging Server