Posted: March 27, 2015 at 5:20 am
Hi, I wanted to reply to my previous topic about the issue I have found regarding the order of the price type elements not working, but the topic is closed. However, though I have constantly updated EE4 to the latest version, the issue seems to be still there. Any update on the status of this bug-fixing? |
|
Hi, in your example here: http://cl.ly/image/3k1a350H0p0P Should the 90 be 72? Also, are the priority conditions (e.g. 5) still the same as in your original example or have those changed? — |
|
Hi Lorenzo, Thanks for your prompt reply. The fee should be 72 (3% of 2400). In the settings I have used at the time of the post (and haven’t changed since) I’m having but %fees set up as “surcharge” (i.e. with priority order 10, but being 2 of the same kind the non-compound calculation should apply?) Here is my settings in price-types: I have tried 2 possible ways In both cases the result is 3090 instead of 2400 + 600 + 72 = 3072 🙁 (ps: I’m not using the “tax” price type because I need to apply those surcharges in this order, so credit card fee after the VAT tax) Thanks! |
|
Hi Vittorio, I ran some testing and had similar results. First, I created a default price type that is surcharge – fixed. Then I created one that is surcharge – percentage. The priority for both is 5. Next, I created a new event with a $10 ticket. I then toggled advanced options via the ticket editor and setup surcharge fixed for $10. Then I setup surcharge percentage for 10%. This is the correct calculation: (base ticket + surcharge fixed) + (base ticket * surcharge percentage) 20 + 1 = 21 However it is running the calculation like this: (10 + 10) + ((10 + 10) * .1) = 22 http://cl.ly/image/103M3W3M1i1P I’m re-opening the bug report so we can have this reviewed again. Thanks — |
|
The support post ‘Price Tye Order Problem (status?)’ 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.