View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|17067||Bug reports||Expression Manager||public||2021-02-08 19:58||2021-03-03 15:00|
|Summary||17067: Expression in array by column does not work|
|Description||Actually 2 errors:|
1. Relevance of column: q5 == "Y" does not seem to work
2. When by accident you type the relevance for the column as q5 = "Y" it changes q5 in the database, where it should give an error message, I guess...
|Steps To Reproduce||Load survey, on first page indicate "Nee"|
On second page observe: Column B still shown, although relevance is q5 == "Y"
On thirdd page observe: q5 suddenly has changed from "N" to "Y" although values should not change through relevance equations.
|Tags||No tags attached.|
|Complete LimeSurvey version number (& build)||3.25.11|
|I will donate to the project if issue is resolved||No|
|Database & DB-Version||MySQL|
|Server OS (if known)||Linux|
|Webserver software & version (if known)||Apache|
limesurvey_survey_642794.lss (23,652 bytes)
|It is much simpler: even typing in 0 for relevance for a column does not work in the array by column question.|
It never work … the issue are "relevance are shown" .
Denis: do you mean that this never has worked before?
What is the use of the relevance field in this question type then? Showing the relevance field actually "promises" that relevances work for columns...
> Denis: do you mean that this never has worked before?
Yes : filter by columns was **never** added in Expression manager
> What is the use of the relevance field in this question type then?
It's an issue
Demo on 3LTS : https://demo.sondages.pro/655577#
Must be improved to be used as question settings (here : apply on whole survey …)
|Is this blocking or should it be something else?|
Not blocking, but misleading. Cost me several hours to detect and make a bug report. While this was already known.
I guess the easiest thing to do is not show relevance fields and perhaps a message that relevance on column level does not work according to bug number such and so. That would be a bummer to the user, but more clear than showing relevance fields that do nothing....
|`partial_block`, and clearly : it's a new issue , we don't have filter on array by column before.|
Temporary solution: take away the relevance field at the columns. It promises something that is not there.
Good solution: make it work....
> Good solution: make it work....
This need a total rewriting of all js done by Expression Manager …
Even my plugin don't hide dynamically the columns …
The your temporary solution are a long solution …
I agree that it should either be hidden or fixed. If fixed is hard, let's hide relevance equation for this question type for subquestions.
> if fixed is hard,
BTW: I have used Denis'solution, this worked in this case.
Same issue? https://bugs.limesurvey.org/view.php?id=16610 "16610: Conditionals with Array Dual Scale not working?"
> 16610: Conditionals with Array Dual Scale not working?
No , not related , maybe issue with condition and number
|2021-02-08 19:58||tammo||New Issue|
|2021-02-08 19:58||tammo||File Added: limesurvey_survey_642794.lss|
|2021-02-09 12:21||tammo||Note Added: 62066|
|2021-02-09 12:21||tammo||File Added: Firefox_Screenshot_2021-02-09T11-18-29.574Z.png|
|2021-02-09 12:22||tammo||Description Updated||View Revisions|
|2021-02-09 12:22||tammo||Steps to Reproduce Updated||View Revisions|
|2021-02-09 12:25||DenisChenu||Note Added: 62067|
|2021-02-09 12:30||tammo||Note Added: 62069|
|2021-02-09 13:19||DenisChenu||Note Added: 62073|
|2021-03-02 19:49||ollehar||Note Added: 62622|
|2021-03-02 19:49||ollehar||Assigned To||=> ollehar|
|2021-03-02 19:49||ollehar||Status||new => feedback|
|2021-03-02 19:57||tammo||Note Added: 62623|
|2021-03-02 19:57||tammo||Status||feedback => assigned|
|2021-03-03 08:16||DenisChenu||Note Added: 62629|
|2021-03-03 10:11||tammo||Note Added: 62630|
|2021-03-03 10:15||DenisChenu||Note Added: 62631|
|2021-03-03 10:20||ollehar||Priority||none => normal|
|2021-03-03 10:20||ollehar||Severity||block => partial_block|
|2021-03-03 10:20||ollehar||Note Added: 62632|
|2021-03-03 10:21||ollehar||Note Edited: 62632||View Revisions|
|2021-03-03 10:22||DenisChenu||Note Added: 62633|
|2021-03-03 12:19||tammo||Note Added: 62634|
|2021-03-03 14:45||ollehar||Note Added: 62650|
|2021-03-03 14:45||ollehar||Note Edited: 62650||View Revisions|
|2021-03-03 15:00||DenisChenu||Note Added: 62659|