View Issue Details

This bug affects 1 person(s).
 2
IDProjectCategoryView StatusLast Update
06234Bug reportsConditionspublic2012-06-24 02:20
ReporterTMSWhite Assigned To 
PrioritynormalSeverityminor 
Status closedResolutionduplicate 
Product Version1.92+ 
Summary06234: unable to AND and OR together sub-questions from same multiple choice question
Description

The conditions editor shows the wrong equation if try to mix AND and OR conditions within the same multiple choice question.

The generated relevance equation, however, is correct.

Steps To Reproduce

I want to create the following equation:

((mc_a.NAOK == "Y") and (mc_b.NAOK == "Y") and (mc_c.NAOK == "Y") and (mc_d.NAOK == "Y" or mc_e.NAOK == "Y" or mc_f.NAOK == "Y"))

But the conditions editor shows the attached.

See attached survey - question q5

TagsNo tags attached.
Attached Files
mc_conditions_error.jpg (39,726 bytes)   
mc_conditions_error.jpg (39,726 bytes)   
Bug heat2
Complete LimeSurvey version number (& build)120613
I will donate to the project if issue is resolvedNo
Browser
Database type & versionMysql 5.3
Server OS (if known)Windows XP
Webserver software & version (if known)XAMPP
PHP Version5.3

Relationships

duplicate of 06188 closedc_schmitz error in conditions generated by editor when selecting several options per sub-question 
related to 06199 closed Survey Rendering Issue for SUBQUESTION (Array) not checked Condition 

Users monitoring this issue

There are no users monitoring this issue.

Activities

TMSWhite

TMSWhite

2012-06-18 16:41

reporter   ~19316

Actually, questions q5-q10 all shows problems. The generated relevance equation is correct in all cases, but the conditions editor consistently has trouble showing accurate logic when ANDs and ORs are mixed in this fashion.

Issue History

Date Modified Username Field Change
2012-06-18 16:26 TMSWhite New Issue
2012-06-18 16:26 TMSWhite File Added: mc_conditions_error.jpg
2012-06-18 16:40 TMSWhite File Added: limesurvey_survey_54265.lss
2012-06-18 16:41 TMSWhite Note Added: 19316
2012-06-18 16:53 TMSWhite Relationship added related to 06188
2012-06-18 16:55 TMSWhite Relationship added related to 06199
2012-06-24 02:20 TMSWhite Relationship replaced duplicate of 06188
2012-06-24 02:20 TMSWhite Status new => closed
2012-06-24 02:20 TMSWhite Resolution open => duplicate