|
Chris
|
February 5, 2013 at 10:41 am
When using additional attendees and promo codes, Event Espresso generates an incorrect (and random) total for the event price.
The event is $200/person. Promo code reduces the price by $125. Five attendees should cost 5 X 200 = $1,000 – 125.00 = $875. The total that I’m getting is $375.
Any help on correcting this would be greatly appreciated.
Using Event Espresso – 3.1.30.3P. but happening on a client’s older version as well.
|
|
Chris
|
February 5, 2013 at 1:45 pm
Ok I think I realized what is going on. It appears that the promo code is being applied to all attendees and not being taken off the top of the final cost. This isn’t how your software used to work. We looked at last years reports and it appeared as if group registrations only had the promo code taken off the final cost.
If I wanted to take an amount off everyone I would use a percentage.
Any help in fixing this issue would be awesome because it is affecting one of our client’s current registrations.
Thanks
|
|
Chris Reynolds
|
February 5, 2013 at 2:03 pm
Ed —
It’s not random. The promo is being applied to each ticket.
( 5 * $200 ) – ( 5 * $125 ) = $375
You are correct, this isn’t the way it worked before. This was a change that was made in the last couple versions when we revised the discount system that was from specific requests for this type of discounting (or rather, complaints that promo codes could not apply discounts to each ticket separately).
|
|
Chris
|
February 5, 2013 at 2:15 pm
Yes I’m sorry I later realized it wasn’t random.
Is there a way I can get the old functionality back. I understand other people would like this feature but changing it up on us has left my client unexpectantly out a few hundred dollars and not having a registration that works the way they need it to. Is there an option to turn the old way back on or a different way of creating a promo code to apply to the entire order?
Thanks for your response
|
|
Chris
|
February 7, 2013 at 2:24 pm
ok quick question:
If I were to comment out lines 203-207 in the use_coupon_code.php would the coupon code then only apply to the primary attendee? Or would I break everything setting our servers on fire thus starting a chain reaction that eventually would end in the apocalypse?
/*
$SQL = "UPDATE " . EVENTS_ATTENDEE_TABLE . ' ';
$SQL .= "SET amount_pd = %f, coupon_code = %s ";
$SQL .= "WHERE registration_id = %d AND id != %d";
$wpdb->query( $wpdb->prepare( $SQL, 0.00, $coupon_code, $registration_ID, $primary_att_id ));
*/
Thanks in advance.
|
|
Dean
|
February 12, 2013 at 3:11 am
Hi Ed,
It is highly possible that it would indeed set the world on fire, causing mass panic and destruction. OR it would just not work.
Im not sure what code the developers have changed to get this to function, with EE being such a complex system it is likely it is not just that one file.
In my tests removing that code made no obvious changes to anything, though I am sure it broke something that I didn’t see.
Honestly if you really need that functionality back I would advise having a look at the code for the latest version and a version which had that functionality and comparing the files using DiffMerge or another diff program.
I must advise though that we do not recommend hacking away at core files and we wouldnt be able to offer support for the changes. Also it will make updating the plugin a nightmare.
|
|
Chris
|
February 13, 2013 at 8:56 am
Hi Dean,
Thank you very much for getting back to me. I really appreciate it. I completely agree that hacking the core is not what I want to be doing for all the reasons that you stated. I just have a client that is disappointed that they had a system that worked the way they expected and now they don’t. So basically I’m getting desperate. I was hoping that there was just a setting that I was missing or possibly something easy I could put in my functions file to fix this issue.
If nothing else I have a feature request to make that a promo code option in the future.
Thanks again for your help.
|
|
Josh
|
February 14, 2013 at 3:36 pm
Hi Ed,
We actually discussed this quite a bit when we made the change. It was a tough call, but the main reason this had to change was in order to allow promo codes to work correctly when using Multi Event Registration. There were limits to what we could do in 3.1, so to make this work, the promo codes had to apply to each ticket.
There were many problems with using promo codes with Multi Event Registration, and we were getting a lot of requests, and quite a few complaints that Multi Event Registration didn’t handle promo codes in a sane way.
We’re planning on making promo codes more flexible in a future release, and there will be a better base for more discount options because the pricing modules in 3.2 are more robust.
|
|
Josh
|
August 18, 2015 at 11:02 am
Update: The Promotions add-on for Event Espresso 4 is now available. It adds the ability to discount a fixed amount from the order instead of applying the discount to each ticket.
|
