Hello community,

In my current K2 installation 2.7.1 I defined ExtraFields as "Textfield". Strangely, I can see 47,00 in the output when I enter the number 47,21 in the backend. If I enter 47.21 (with point as a separator) then I see in the output correctly with 47,21.

But in my items there are several such fields and with some it also works with "," (colon) as separator and on others only with "." (point).
I have checked the settings in the database in the table "k2_extra_fields" for the different fields which are all "Textfield". The settings are exactly the very same, but the behaviour is different.
You can see this at the screenshot imgur.com/a/rQOGh. In the field "Nutzfläche" I HAVE to enter point as seperator that also the decimal places in the output are represented whereas in the field "Loggia" I can enter the colon as separator and nevertheless in the output the decimal places are represented correctly, so why not also in the "Nutzfläche" field?
Please see www.rhw.co.at/immobilien-rhw/wohnen/miete/objektdetail/3-zimmer-erstbezug-mit-loggia-3.html

Please can you help me how to set things up that our customer only have to enter "," (colon) here and do not have to use a mixed form?
Colon is the standard used separator here in Austria for decimal places.

Thanks in advance
OASE

Hello,
Are you using a text extrafield?

Hello,

yes in the backend under "Extra Fields" the type is stated as "Text Field".
As you can see here: imgur.com/a/l4Hap

I can see the fields working fine now on your site.
Are you using any scripts which alter the frontend?

Not that I would know about it. Where can i find out, whether a script is altering the frontend or not?

In the frontend the decimal places schow up correctly right now because in the backend we use point and comma mixed mode for the given fields.

I cannot verify the issue.
Which ever I use (colon, comma, semicolon) the text does is get altered.
imgur.com/a/Lh4HZ

Make sure to use K2's latest version and ask the template's developer of there is extra functionality in the extrafields.

Thats the wired thing. I also have fields where comma is working well.
Out customer told us, when he creates a new field there is no problem but on old fields. Could this be related to some version change in K2?

Template is fom TemPlaza "Interiart". I'll try my luck with their support :-)

Anyway any help will be appreciated.

With the template provider we found the problem,

in the file: templates\tz_interiart\html\com_k2\default\item.php there were code altered which lead to the described behaviour.

Now as i know where the problem comes from, I can handle it.

Thank you for you help!!

Nice to hear that you got it sorted out :)