View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|12266||Feature requests||[All Projects] Conditions||public||2017-04-11 15:34||2017-04-11 15:34|
|Target Version||Fixed in Version|
|Summary||12266: Condition incorrectly parsed when using more than two possible values for a token attribute|
|Description||It's not possible to have a condition that consists of more than two values of a token.|
For example. A condition that is displayed like this in the condition designer:
First name [Inexistant token table] equals john
First name [Inexistant token table] equals alice
First name [Inexistant token table] equals bob
Will be written as:
((TOKEN:FIRSTNAME == "alice" or TOKEN:FIRSTNAME == "bob") and (TOKEN:FIRSTNAME == "john"))
Obviously, this will never evaluate to True.
|Additional Information||This bug is introduced in Version 2.50+ Build 160725, see also https://bugs.limesurvey.org/view.php?id=11412.|
The uploaded lss file includes the string ((TOKEN:FIRSTNAME == "alice" or TOKEN:FIRSTNAME == "bob") and (TOKEN:FIRSTNAME == "john")), but will show the correct condition in the condition designer.
|Tags||No tags attached.|