woowarn

Thousand or ‘,’ coma inside woocommerce price not supported

8 Comments

  1. Andrew T.
    December 2, 2019 @ 2:56 pm

    Seconded.

    This really needs to be made a priority.

    Any prices which are over 1000, Price Comparison Pro puts a “,” into the price, like this: “1,000”.

    However, the Woocommerce Price box does not accept the comma “,” as it only allows it to be a full stop.

    Changing the Settings in Woocommerce > General > Currency Options doesn’t seem to help or do anything.

    Reply

    • Dave H.
      December 18, 2019 @ 8:01 am

      Prioritising. I’ll get a fix out asap.

      Reply

      • Andrew T.
        January 15, 2020 @ 9:06 am

        Great, thank you! Looking forward to getting this working so that we can continue the development of our new site.

        Reply

      • Andrew T.
        February 13, 2020 @ 12:00 pm

        Hi Dave,
        Any news on a fix yet?
        Many thanks.

        Reply

        • Andrew T.
          February 19, 2020 @ 3:35 pm

          If someone else can test it…I think that this issue has now been resolved.

          Not sure if you were somehow able to push out a fix Dave or if it was a WordPress/Woocommerce update that fixed it, but my prices over £999 (such as £1,499.00) are now updating as intended with the correct commas and full stops.

          Reply

          • Dave H.
            April 15, 2020 @ 11:06 am

            That’s great news! I was really surprised by this issue because I’d never experienced it personally.

            Is it possible that you’d updated WooCommerce but not updated the database or something? I guess it might have been fixed in a WooCommerce update.

            The only thing Woo say about this is that they use the PHP Locale to determine price formatting. They have an option for decimal and thousands separators in their settings pages, but this is only for DISPLAY not for reading and interpreting data coming in.

            https://github.com/woocommerce/woocommerce/issues/25864

  2. Dave H.
    June 30, 2020 @ 3:52 pm

    This has been implemented in beta 3.73.

    Specifically, I’ve added a decimal symbol config to allow you to choose if it should presume , or . or something else is the decimal separator.

    Also, I had to code something up for websites similar to bol.com which are actually using spans with images inside them for the decimal separator. When this gets scraped, it turns into whitespace, e.g. 19.99 becomes 19 99, so now if there is no decimal separator present in the scraped results, it will replace the whitespace with a decimal place to product 19.99.

    Reply

  3. Dave H.
    June 30, 2020 @ 3:52 pm

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

We use cookies

We use cookies for various things on our site, including our on-site chat bubble (if you use it), our comment forms (if you use them) and for session handling (if you log in).

Other than that, we use cookies to identify where traffic came from to help us understand which traffic turns into sales, we use a cookie for Google Analytics traffic analysis and we use a cookie to customise adverts for our own products we think you'll be interested in.

You can read more detail in our privacy policy page. Please click 'Accept' or 'Decline' to continue.