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 Groupon value problem | Event Espresso - Staging Server
I had thought this was fixed at one point, but again I have noticed that when a groupon is redeemed for a class, it is comps the registration at 100 % regardless of how many tickets are purchased.
Example: class value is $35. Groupon should comp 1 ticket only.
Customer selects 7 tickets, enters 1 groupon code, and all 7 tickets are covered by the groupon.
What should happen is that 6 tickets should be paid for with only 1 ticket comped by the Groupon.
This is a major flaw in the groupon implementation I had seen before, but for then thought it was fixed. I could be mistaken but would appreciate seeing it fixed ASAP. Otherwise I have to turn group registrations off which is very frustrating to paying customers.
The Groupon Integration add-on does not currently check for number of attendees in the registration. What you may be thinking about is the issue in which a Groupon code would discount all events in a Multi Event Registration cart checkout — which has been fixed — now only the event with Groupons enabled gets the discount. We are planning on building a 2.0 version of the Groupon / Social Coupons add-on that hooks better into their system. If we made the Groupon such that only a single ticket was discounted, we’d immediately get backlash from people who are using Groupons with multiple tickets included in the Groupon. Currently we don’t recommend having group registration turned on for events that have Groupons active.
Viewing 1 reply thread
The support post ‘Groupon value problem’ 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.