View Issue Details

This bug affects 1 person(s).
 8
IDProjectCategoryView StatusLast Update
04676Bug reportsConditionspublic2010-11-17 01:03
Reporternasprok Assigned Tolemeur  
PriorityurgentSeveritypartial_block 
Status closedResolutionfixed 
Product Version1.90+ 
Fixed in Version1.91beta 
Summary04676: Conditions on rankings still only work until ranking 9
Description

Still not fixed. Issues with large survey. You can see the problem on the following URL. http://195.134.82.11/lime/limesurvey/index.php?sid=93951&newtest=Y&lang=el .
The problem appears in page #6 with the 32 options.

Additional Information

Reported again in 04308

TagsNo tags attached.
Attached Files
Bug heat8
Complete LimeSurvey version number (& build)9229
I will donate to the project if issue is resolved
BrowserAll
Database type & versionMYSQL - 5.1.41
Server OS (if known)Windows XP
Webserver software & version (if known)Apache/2.2.14
PHP Version5.3.1

Users monitoring this issue

There are no users monitoring this issue.

Activities

lemeur

lemeur

2010-10-14 07:38

developer   ~13164

I have very limited time so please try to be more explicit:

  • explain how you expect LS to behave, and what you see as a bug
  • attach a test survey in English (possibly a simplified one) in this ticket
  • describe the detailed steps to reproduce the issue

Without this there is a high possibility that the ticket won't be handled before a long time.

nasprok

nasprok

2010-10-14 09:47

reporter   ~13165

I'm terribly sorry to waste your time by not being more specific. I created a new survey in English and I attached it. The URL for the survey is http://195.134.82.11/lime/limesurvey/index.php?sid=77786&newtest=Y&lang=en
There is a question where I ask a doctor how many patients visit him/her during a week (1 to 21). Based on their answer they should then fill in their diagnosis for each patient. For example if they choose #12, 12 Patient Records should appear. So I created conditions for each patient record saying "If answer in the first question is greater than or equal to ..."
The problem is:
When they choose number 1 everything works fine
When they choose number 2, patient records 1,2 appear but also 10-19!
When they choose number 3, patient records 1,2,3 appear but also 10-21!
The behavior is similar for choices up to 9
When they choose number 10, only patient records 1,10
When they choose numbers between 11 and 19, patient records 1 and 10 up to their choice appear!
*Finaly when the choose 20 or 21, patient record 1,2 and 10 up to their choice appear!

It seems that the check for choices greater than 9 isn't working.

lemeur

lemeur

2010-10-14 09:52

developer   ~13166

Last edited: 2010-10-14 09:52

[Quote]I'm terribly sorry to waste your time by not being more specific.[/Quote]
Don't worry, you have not wasted my time, I just wanted you to help me save some time while investigating this ticket, which you just did :-)
Thanks.

Is the survey you've uploaded confidential (in this case I will mark the ticket as private) ?

I'll have a look as soon as possible and let you know.
Regards,
Thibault

nasprok

nasprok

2010-10-14 09:59

reporter   ~13167

No it isn't! You can leave it public because the data I used is random, just to demonstrate the problem.
Thank you for you time!

Mazi

Mazi

2010-10-14 14:53

updater   ~13174

I can reproduce the problem using the attched survey.

@nasprok: Can you check what happens if you change the condition e.g. from "greater or equal to '10'"
TO
"greater than '9'"

nasprok

nasprok

2010-10-14 21:14

reporter   ~13191

Last edited: 2010-10-14 23:39

@Mazi: I changed the condition for choice 10 as you suggested and now when I choose 10 only Patient 1 appear. Also tried that for choice 21 to see what happens when the first of the two digits changes and patient records 1,2 and 11 through 21 appear. I'm unable to find the pattern of the problem so I can help you more.

lemeur

lemeur

2010-10-16 22:30

developer   ~13217

This is no bug.
This question type is not supposed to get Numerical answers. Thus the comparizon is based on string comparizons where "2" > "10" for instance.

The quick fix for your issue is to replace in you first question the codes for 1 to 9 to "01" to "09", and then to re-define the conditions for the following 9 questions.

nasprok

nasprok

2010-10-17 00:09

reporter   ~13221

OK!!! I feel sooo stupid! I never realized that the comparison isn't numerical. You should delete this issue so I wont embarrass myself anymore ;-)

lemeur

lemeur

2010-10-17 07:31

developer   ~13222

Last edited: 2010-10-17 07:34

[QUOTE]OK!!! I feel sooo stupid![/QUOTE]
Don't feel stupid, you're not. This feature is just confusing.
I am partly responsible for this.
When the greater/lower conditional operator was implemented (not by me), the developper just didn't think about this: this made the operator only work for string comparizons.
I fixed this so that for questions having only numerical answers, the comparizon switches to Numerical comparizon. This was an easy way to avoid breaking old surveys where comparizons are used to compare Strings.
However the true question is: Is there anyone in the LS commmunity who uses String comparizon at all! I can think of some use of this, but this must be very rare.

Mazi

Mazi

2010-10-18 12:09

updater   ~13228

I have never used string comparison all the time I used Limesurvey.

lemeur

lemeur

2010-11-13 09:54

developer   ~13520

I've decided to implement Numerical comparizon by default in version 1.91.
This fixes this issue.

Thibault

c_schmitz

c_schmitz

2010-11-17 01:03

administrator   ~13540

Fix released in latest 1.90+ version.

Issue History

Date Modified Username Field Change
2010-10-14 01:43 nasprok New Issue
2010-10-14 01:43 nasprok Status new => assigned
2010-10-14 01:43 nasprok Assigned To => lemeur
2010-10-14 07:38 lemeur Note Added: 13164
2010-10-14 07:38 lemeur Status assigned => feedback
2010-10-14 09:11 nasprok File Added: limesurvey_survey_77786.lss
2010-10-14 09:47 nasprok Note Added: 13165
2010-10-14 09:47 nasprok Status feedback => assigned
2010-10-14 09:52 lemeur Note Added: 13166
2010-10-14 09:52 lemeur Note Edited: 13166
2010-10-14 09:59 nasprok Note Added: 13167
2010-10-14 14:53 Mazi Note Added: 13174
2010-10-14 14:57 Mazi Status assigned => feedback
2010-10-14 21:14 nasprok Note Added: 13191
2010-10-14 21:14 nasprok Status feedback => assigned
2010-10-14 23:39 nasprok Note Edited: 13191
2010-10-16 22:30 lemeur Note Added: 13217
2010-10-16 22:30 lemeur Status assigned => feedback
2010-10-17 00:09 nasprok Note Added: 13221
2010-10-17 00:09 nasprok Status feedback => assigned
2010-10-17 07:31 lemeur Note Added: 13222
2010-10-17 07:31 lemeur Note Edited: 13222
2010-10-17 07:32 lemeur Note Edited: 13222
2010-10-17 07:34 lemeur Note Edited: 13222
2010-10-17 07:34 lemeur Note Edited: 13222
2010-10-18 12:09 Mazi Note Added: 13228
2010-11-13 09:54 lemeur Note Added: 13520
2010-11-13 09:54 lemeur Status assigned => resolved
2010-11-13 09:54 lemeur Fixed in Version => 1.91beta
2010-11-13 09:54 lemeur Resolution open => fixed
2010-11-17 01:03 c_schmitz Note Added: 13540
2010-11-17 01:03 c_schmitz Status resolved => closed