Support

Home Forums Event Espresso Premium Increase number of decimal places in price modifier

Increase number of decimal places in price modifier

Posted: August 30, 2017 at 12:35 pm


beyondsquare

August 30, 2017 at 12:35 pm

Hi,

I’m creating a event where users can buy individual tickets or ticket bundles. The bundle is essentially buy 21 tickets only pay for 20. I’ve set up the ticket bundle so that the minimum and maximum number of tickets is 21 however due to the maths involved, if I changed the ticket price it’s still always out by a few cents due to rounding.
The same happens if I have the tickets at full price and try and use a % price modifier as discounting to 2 decimal places is not specific enough. Is there any way to increase the number of decimal places you can set the discount to.


Josh

  • Support Staff

August 30, 2017 at 4:54 pm

Hi there,

I checked and there isn’t a way to increase the number of decimal places for those inputs beyond 3 decimal places. I wonder how many decimal places would actually be enough to make a 21 ticket bundle price to work out to be exactly the same as a 20 ticket bundle price. Do you have an estimate about how many would be required to make that happen?

The support post ‘Increase number of decimal places in price modifier’ 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.

Support forum for Event Espresso 3 and Event Espresso 4.
Documentation for EE3 and EE4
Documentation for Event Espresso 3

Documentation for Event Espresso 4

Status: closed

Updated by  Josh 2 years, 2 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Do NOT follow this link or you will be banned from the site!
[for="input_96_5_3"]
[for="input_96_5_3"]
[gravityform id=96 title=false description=false]
  • This field is for validation purposes and should be left unchanged.
[i]
[i]
[gravityform id=69 title=false description=false]
  • This field is for validation purposes and should be left unchanged.