Problem with ticket prices like 18,50 €

  • Resolved grobc

    (@grobc)


    3 years, 2 months ago

    If I configure decimal pricing for tickets and click the posts save button, or after I have changed the price from a full amount to a to a decimal price and use the update button, the following message appears:

    “Enter a valid value. The two closest valid values ​​are 18 and 19”

    and it doesn’t matter, if I use 18.5 or 18,5

    Thanks for your help

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author Joe Dolson

    (@joedolson)

    3 years, 2 months ago

    Can you share a screenshot of that error message? I don’t recognize the error language, so I’m not sure where it’s coming from.

    Thread Starter grobc

    (@grobc)

    3 years, 2 months ago

    Hi Joe,
    if I set no default price at /wp-admin/admin.php?page=mt-ticketing I get the following message.

    https://i.ibb.co/R45CHB6/Bildschirm-foto-2023-02-19-um-21-48-41.png

    If I set the default price for example to 18,5 and add a new ticket, I can set the price to 18,5 and any other price with xx,5, but so it´s not possible to sell tickets for 18€ or 8,60€, as example.

    https://i.ibb.co/ZWmfByn/Bildschirm-foto-2023-02-19-um-22-07-16.png

    So right now I have to change the default price to the desired one if I like to add a actual ticket ..
    Same if I like to change the price for an existing one…

    • This reply was modified 3 years, 2 months ago by grobc.
    • This reply was modified 3 years, 2 months ago by grobc.
    • This reply was modified 3 years, 2 months ago by grobc.
    Plugin Author Joe Dolson

    (@joedolson)

    3 years, 2 months ago

    The only impact setting a default price has on ticket sales is that it pre-fills the values when you create a new event. The actual prices used are whatever you set in the event.

    I did some looking, and the error message you’re seeing appears to be a Firefox invalid step value error, but the values you’re describing aren’t errors.

    You do have to set prices using decimal points: 18.5 or 8.6; these are numbers, not currency displays, so the value has to be numeric, rather than formatted. All formatting is done separately on the front-end.

    Thread Starter grobc

    (@grobc)

    3 years, 2 months ago

    It´s the same, if I use decimal points.

    https://i.ibb.co/1nGXH4n/Bildschirm-foto-2023-02-19-um-22-47-47.png

    If you like, I can set up admin login.

    Thanks
    Carsten

    Plugin Author Joe Dolson

    (@joedolson)

    3 years, 2 months ago

    If you have a dev environment, that’s preferable over production. You can send me an email at my contact form with any additional information.

    Thread Starter grobc

    (@grobc)

    3 years, 2 months ago

    I wrote you an mail. But I also figured out, that if I add the step attribut to the input field via the browsers developer view, I am able to save the different prices, with or without decimal number.

    https://i.ibb.co/JR0mK4s/Bildschirm-foto-2023-02-19-um-23-39-10.png

    Plugin Author Joe Dolson

    (@joedolson)

    3 years, 2 months ago

    I just followed up with a fix; same thing. You won’t need to do the verification step I suggested, since doing the browser edit accomplishes the same thing. I’ll get an update out as soon as I can.

    Thread Starter grobc

    (@grobc)

    3 years, 2 months ago

    THANKS!!

    Thread Starter grobc

    (@grobc)

    3 years, 2 months ago

    Great Service, great plugin!!!
    The problem was solved the same day, the update was released one day later!

    Thanks
    Carsten

Viewing 9 replies - 1 through 9 (of 9 total)

The topic ‘Problem with ticket prices like 18,50 €’ is closed to new replies.