|
sara.bosman
|
June 14, 2023 at 6:35 am
Since last update, the total ticket price is zero when the base price is zero, even when there are several non-zero modifiers. We use those modifiers because our ticket price calculation is quite complex. I believe this behaviour is wrong; the total should be the total, like before. A screenshot:
Is there a solution or quick fix to correct this?
|
|
sara.bosman
|
June 14, 2023 at 6:37 am
(forgot to check the notify follow-ups checkbox behow this post – done)
|
|
sara.bosman
|
June 14, 2023 at 7:42 am
UPDATE: manually setting the total in the database (wp_esp_ticket:TKT_price) seems to work for now, but this is not a long-term workable solution of course
|
|
Garth
|
June 14, 2023 at 10:27 am
I’m pretty certain there is a fix for this that is already for release in the next version (5.0.8).
|
|
sara.bosman
|
June 14, 2023 at 10:59 am
Ok, looking forward.
Oh, and another bug in the same window: when I want to enter e.g. 456.78, it doesn’t accept the dot, so I first have to type the price without it, 45678, and then I have to edit the field again and add the dot. Very annoying. And it also seems to automatically remove trailing zeroes while typing, which can be annoying too. E.g. when I want to change 10.05 to 10.15, and I remove the trailing 5, it autocorrects 10.0 to 10, and I’m stuck typing the dot again.
|
|
Garth
|
June 14, 2023 at 11:36 am
The decimal is a known issue too, no fix yet because we’re digging through the dependencies of libraries to find out what changed.
|
