I’m not sure if I understand your question. By ‘regular price,’ are you talking about the base price of the product, the price with no additions? And would ‘offer price’ be the price of the individual variations? I’ve never seen a situation where decimal numbers do not work and can’t think of how that would be possible. But here are some things you might look at.
- The most common issue is that people expect the variation price to update automatically instead of reapplying the markup (surcharge). It does not sound like this is your problem.
- You may want to check if the ‘Round Markup’ setting is set in the Settings. This only applies to percentage markups, and only to the amount below the decimal, so I don’t think this is the issue, either.
Unfortunately, that’s all I can think of. Please help me understand the issue better.
As soon as I enter a decimal number as the regular price/base price or offer price, the markup for the variant is not applied.
For Example a Shirt costs regular 45€. Extra front print as a variant 2,50€. So regular 47,50€. The offer price is 29,75€ without print. So with print 32,25€. But the offer price remains at 29,75€. Markup does not add the surcharge. If I enter 30€ as offer price, Markup correctly adds the 2.50€ to 32.50€.
Bingo! I was able to recreate the problem. The issue is related to how PHP’s “is_numeric()” function handles decimals (it doesn’t like commas).
My test data already had a $2.50 markup, so when I switched to Euro notation for testing, I didn’t need to create a new markup. But when I deleted the existing markup and tried to recreate it using “2,50€”, the problem emerged. (You likely encountered an issue when trying to enter markup values on the Attribute page.) This explains why the bug didn’t surface in my testing before the last release.
I’ve resolved the problem in both the markup validation and price processing functions, and will be rolling out a new release as soon as I complete regression testing. I hope to have this completed by the end of today.
Thank you for your patience and for providing information that helped me track this down.
I guess everything takes longer than expected, but I’m confident version 4.3.8 will resolve your issue. I’ve just rolled it out; please let me know if it works for you.
Thanks.
It works perfectly! Thank you very much!