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 One more vote for applying Groupons to tickets rather than events | Event Espresso - Staging Server
Loving the plugin. :-) If you’re still working on the latest upgrade, I’d like to vote again for applying Groupons to tickets OR events, if possible.
My client sells tickets to wine tasting classes. Her Groupon deal is a 2-for-1 type where a Groupon entitles the purchaser to two tickets to a class. So when they redeem the voucher, they have to purchase two tickets: no more, no less. She doesn’t want to have to track each and every transaction on the site. So what she wants to do is have to either (a) automatically select two tickets when using a Groupon or similar code or (b) – my recommendation – create two ticket levels, one for regular purchase that does not accept Groupon and one that makes Groupon available with max and min tickets set to 2.
Am I making any sense?
Thanks again – I’ve been able to create a wonderful custom ticketing solution for my client and I’m recommending your plugin to other web colleagues who are still fighting with WooCommerce for ticketing. ;-)
Thanks for the feedback! Your points definitely make sense and I will add your +1 to the feature request list.
Viewing 1 reply thread
The support post ‘One more vote for applying Groupons to tickets rather than events’ 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.