The error with thousands separator doesn't appear when pressing the "Previous" button in the survey, but the decimal mess does.

i confirm the same scenario

Hello and happy new year.

I went from 150629 the last version dated: 151 205 successfully ..
short because users of some questionnaires were reassembled errors when entering numerical values.

I looked in detail the type of question that is the problem:

1. Digital input
2. Multiple digital input.

The bugs are critical about the content of the data: the application is not planted, but the content of the answers is completely distorted.
Existing bugs treat problems:

1. numerical Input: bugs.limesurvey.org/view.php id = 10189?

   ---

   We created a basic questionnaire (2 groups each with 2 questions: numerical input and multi numerical input )
   choose for the numerical input:
   Only integer -> yes
   That's all.
   We made the questionnaire and a value is entered in thousands (eg 200 000).
   It is found that:
   thousands separator is automatically (though we did not ask).
   The entry box appears well 200,000
   We go to the next group and back to the previous :
   The input box appears only 200. This value is the one that is saved in the database and that can be exported to Excel.

We redo the same operation, but enter 2 million.
We go to the next group, there was a crash which indicates that the data could not be saved.
His answers to be deleted and we are told that our session expired.
If you look in foreclosures answers, we will see an incomplete response with the value 200.

Variation: add the thousands separator in the setting of the question ---> it becomes very attractive to the eye, but madness to explain to users.

Option 2: choose as decimal separator point not comma : what it looks after with thousands separator?

2. Multiple digital input:
   bugs.limesurvey.org/view.php?id=9648
   bugs.limesurvey.org/view.php?id=9508
   www.limesurvey.org/en/forum/can-i-do-thi...eric-inputs?start=45

   ---

   We return to the same basic survey
   Thousands separator is indicated in the parameter.
   That's all.
   We made the questionnaire and set 20 000 for example.
   We go to the next group (the stored value is 200) and back to the previous :
   The entry box displays 2.00
   If we go back to the next group, the value that will be stored in the 2 answers ( and full zero back).

The display will be the following answers to the entered value of 20,000: 200.0000000000.
This will also be the value to be exported in csv or excel file.

Variation: enter 200 000 as the value -> was a crash which indicates that the data could not be saved.
His answers to be deleted and we are told that our session expired.

@Denis: Currently it is a feature, but for me it's more of bug - crash. You can change?

@ervit : i move it to "bug" not feature request .

Can you confirm it's a duplicate than https://bugs.limesurvey.org/view.php?id=9876 ?

The bug is "thousand separator" + "," for decimal : all is broken .

@Denis https://bugs.limesurvey.org/view.php?id=9876 seems to be about other issues, although it can be related to the same input mask implementation.

PS: i was sure i was reporting a bug and not a feature request... must have overlooked

FYI: This will be fixed in 2.5, not 2.06.

Fix committed to master branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=17571

The first issue is resolved, the second (going back and forth) is not.

Fixed in 2.5. Please update at next release and confirm.

Version 2.50+ Build 160223 released