View Issue Details

This issue affects 1 person(s).
 6
IDProjectCategoryView StatusLast Update
18334Bug reportsData Entry (non public)public2022-09-08 14:44
Reporterinterval Assigned Toollehar  
PrioritynoneSeverityminor 
Status closedResolutionwon't fix 
Product Version5.3.x 
Summary18334: Automatic Transformation of number using thousands separator
Description

Question type: numerical input. If a participant of the survey types in a number with thousands separator (e.g. "1.000"), then LimeSurvey transforms the response automatically to number “1”

Steps To Reproduce

Steps to reproduce

(Replace this text with detailed step-by-step instructions on how to reproduce the issue)

Expected result

(Write here what you expected to happen)

Actual result

(Write here what happened instead)

TagsNo tags attached.
Bug heat6
Complete LimeSurvey version number (& build)Version 5.3.31
I will donate to the project if issue is resolvedNo
BrowserFirefox
Database type & version?
Server OS (if known)
Webserver software & version (if known)
PHP Version?

Users monitoring this issue

There are no users monitoring this issue.

Activities

ollehar

ollehar

2022-09-05 15:23

administrator   ~71599

Separators are different in different countries. Don't use separators.

gabrieljenik

gabrieljenik

2022-09-05 15:36

manager   ~71600

Will try to reproduce

interval

interval

2022-09-05 15:57

reporter   ~71601

Thanks for your quick reply . Not using a thousands separator at all is actually no good solution for us, since we do not want to warn the participants before every numeric question that they are not allowed to use it.

ollehar

ollehar

2022-09-05 16:07

administrator   ~71602

It should be filtered, no?

interval

interval

2022-09-05 16:16

reporter   ~71603

What should be filtered?

ollehar

ollehar

2022-09-05 16:17

administrator   ~71604

Last edited: 2022-09-05 16:18

Invalid numbers like "1,00" or "1.00" should be filtered when written to "1" so that the participant knows. Same with "1'00" etc etc.

Unless you want to allow decimals, of course.

interval

interval

2022-09-05 16:38

reporter   ~71605

Yes, most of the time we want to use decimals (in our case a comma).
But even if we don't want to use decimals and don't allow them, then there is still a bug and LimeSurvey will still transform "1.000" (or "1,000") into a "1" without giving a hint to the participant. I bet most people don't even notice and hence do not know that LimeSurvey automatically transforms a "." (from 1.000) to a "," (which will then turn out as number "1").

gabrieljenik

gabrieljenik

2022-09-08 14:30

manager   ~71653

I think there could be 2 problems here:
1 - There is no place to set thousand and decimal separator. Am I missing it?
2 - Even if we say the point is decimal, the thusand searator is not allowed.

Thoughts?

image.png (21,124 bytes)   
image.png (21,124 bytes)   
ollehar

ollehar

2022-09-08 14:32

administrator   ~71654

Last edited: 2022-09-08 14:33

This was discussed extensively in 2015 and 2016. It's just a mess to get right with all different locales. Just don't use a numeric type, use a normal text question, and then write your own regular expression if you really want to validate it.

gabrieljenik

gabrieljenik

2022-09-08 14:36

manager   ~71655

Perfect! Then I think it is OK to close the ticket, right?

interval

interval

2022-09-08 14:40

reporter   ~71656

Alright, then we will probably use a normal text question and check the answers afterwards.
Ticket can be closed, thanks for your advice!

ollehar

ollehar

2022-09-08 14:44

administrator   ~71657

Feel free to discuss further on forum, for more advice on how to design regular expression etc. \o

Issue History

Date Modified Username Field Change
2022-09-05 14:29 interval New Issue
2022-09-05 15:23 ollehar Note Added: 71599
2022-09-05 15:23 ollehar Bug heat 6 => 8
2022-09-05 15:36 gabrieljenik Status new => acknowledged
2022-09-05 15:36 gabrieljenik Note Added: 71600
2022-09-05 15:36 gabrieljenik Bug heat 8 => 10
2022-09-05 15:57 interval Note Added: 71601
2022-09-05 15:57 interval Bug heat 10 => 12
2022-09-05 16:07 ollehar Note Added: 71602
2022-09-05 16:16 interval Note Added: 71603
2022-09-05 16:17 ollehar Note Added: 71604
2022-09-05 16:18 ollehar Note Edited: 71604
2022-09-05 16:38 interval Note Added: 71605
2022-09-06 15:42 gabrieljenik View Status private => public
2022-09-06 15:42 gabrieljenik Bug heat 12 => 6
2022-09-08 10:53 Ondricka Bug heat 6 => 8
2022-09-08 12:36 ollehar Bug heat 8 => 6
2022-09-08 14:30 gabrieljenik Note Added: 71653
2022-09-08 14:30 gabrieljenik File Added: image.png
2022-09-08 14:32 ollehar Note Added: 71654
2022-09-08 14:33 ollehar Note Edited: 71654
2022-09-08 14:36 gabrieljenik Note Added: 71655
2022-09-08 14:40 interval Note Added: 71656
2022-09-08 14:44 ollehar Assigned To => ollehar
2022-09-08 14:44 ollehar Status acknowledged => closed
2022-09-08 14:44 ollehar Resolution open => won't fix
2022-09-08 14:44 ollehar Note Added: 71657