View Issue Details

This bug affects 1 person(s).
 6
IDProjectCategoryView StatusLast Update
13531Bug reportsConditionspublic2021-03-10 21:39
Reporterblocka Assigned Toollehar  
PrioritynoneSeverityminor 
Status closedResolutionno change required 
Product Version3.3.x 
Summary13531: No recorded responses for a displayed question
Description

I have a survey with a numeric input type question (Q42) followed by an Array (1-5) -- Q43.

The array question (Q43) had a condition on it to only display if :

((Q42.NAOK > " "))

When testing this survey, if I left Q42 blank, then Q43 was hidden, and if I entered a value, Q43 was shown, as expected.

I understand in restrospect that I should have used !is_empty(Q42) instead ... however my testing showed that Q43 was displayed.

I activated the survey, and after collecting data from 10,000+ respondents, discovered that in all cases responses Q43 was blank. Q43 wasn't set to mandatory, but with the number of respondents, it seems unlikely that anyone who entered a value for Q42 would skip Q43.

My survey format was set to "Group by Group"... and Q43 appeared but ....

... I did discover that I run my survey with format "question by question" q43 is NEVER displayed (and so -> no answers). In format "group by group" q43 is displayed, but handled as if not displayed -> no answers.

TagsNo tags attached.
Attached Files
survey_779287.lss (21,248 bytes)
Bug heat6
Complete LimeSurvey version number (& build)2.73.0 b171219 (but confirmed in latest LS 3 release as well)
I will donate to the project if issue is resolvedNo
Browser
Database type & versionmySQL 5.6.37
Server OS (if known)CentOs
Webserver software & version (if known)Apache
PHP Version7.0.x

Users monitoring this issue

There are no users monitoring this issue.

Activities

DenisChenu

DenisChenu

2018-03-25 11:49

developer   ~47208

We add some '' in test for expression : https://github.com/LimeSurvey/LimeSurvey/commit/e8a42231651bdea5c1c2f1e88b8b0d382fbbc131

Strange this was not fixed after testing and improve system :/

ollehar

ollehar

2018-03-26 10:11

administrator   ~47212

This again? I didn't get the time to fix it completely before. I think the recommended solution is to never compare with empty string.

LouisGac

LouisGac

2018-05-16 13:42

developer   ~47644

so, where are we with this bug olle?

ollehar

ollehar

2018-05-16 14:20

administrator   ~47650

Right now: I'll never have time to fix it completely. Unless Carsten decides to make it a priority.

LouisGac

LouisGac

2018-05-16 14:59

developer   ~47653

ok

Issue History

Date Modified Username Field Change
2018-03-24 20:08 blocka New Issue
2018-03-24 20:08 blocka File Added: survey_779287.lss
2018-03-25 11:49 DenisChenu Note Added: 47208
2018-03-26 10:11 ollehar Note Added: 47212
2018-05-16 13:42 LouisGac Assigned To => ollehar
2018-05-16 13:42 LouisGac Status new => assigned
2018-05-16 13:42 LouisGac Note Added: 47644
2018-05-16 14:20 ollehar Note Added: 47650
2018-05-16 14:59 LouisGac Note Added: 47653
2021-03-10 21:39 ollehar Status assigned => closed
2021-03-10 21:39 ollehar Resolution open => no change required