View Issue Details

This issue affects 1 person(s).
 6
IDProjectCategoryView StatusLast Update
06004Bug reportsConditionspublic2012-05-10 12:22
ReporterResearchOnBlogs Assigned ToTMSWhite  
PrioritynormalSeverityminor 
Status closedResolutionno change required 
Product Version1.92+ 
Fixed in Version1.92+ 
Summary06004: show/hide question via condition - child question is not cleared after changing parent question
Description

If you show/hide question via condition, the child question is not cleared after changing parent question.

Steps To Reproduce

Question 1: Yes/No

Question 2: A/B/C (only shown if Q. 1 is "yes")

If you check first "yes" and check Q. 2 "A" AND AFTER THAT check Q 1 "No", Q2 will be hidden (right), but the checked answer of Q2 is stored and not cleared

TagsNo tags attached.
Attached Files
Bug heat6
Complete LimeSurvey version number (& build)120405
I will donate to the project if issue is resolvedNo
Browser
Database type & versionx
Server OS (if known)x
Webserver software & version (if known)x
PHP Versionx
Git branch / Pull Request URL

Users monitoring this issue

There are no users monitoring this issue.

Activities

TMSWhite

TMSWhite

2012-04-11 15:44

reporter   ~18317

Please attach the actual survey that demonstrates this problem.

If you are using a custom template, please confirm that you are seeing a problem with one of the default templates.

TMSWhite

TMSWhite

2012-04-12 15:42

reporter   ~18338

There is insufficient detail to replicate the problem. Please attach a sample survey that demonstrates the issue.

TMSWhite

TMSWhite

2012-04-13 04:45

reporter   ~18344

I am unable to replicate - unless there is a mis-understanding of how the new system works. If you are saying that the value of Q2 is stored in the database when Q1 is No, then that is wrong - please attach a survey demonstrating it since I can't replicate that behavior with any of our many test surveys.

Perhaps, instead, you are saying that you see this behavior:
(1) Q1- select "Yes", which shows Q2
(2) Q2- select A
(3) Q1- select "No", which hides Q2
(4) Q1- select "Yes", which shows Q2 again, and you see it still has the value of A

If so, this is the new and desired behavior of 1.92. That way if you have cascading relevance and a user changes her mind, she does not have to re-enter data. However, irrelevant data is not submitted. If you follow steps 1-3, click next, then click previous, you will see that the value for Q2 is now blank.

Mazi

Mazi

2012-04-16 22:37

updater   ~18395

This might be related to the "deletenonvalues" setting (see http://docs.limesurvey.org/Optional+settings&structure=English+Instructions+for+LimeSurvey#Survey_Behavior):
"$deletenonvalues: This is a fairly difficult setting to explain. If set to 0, if a question (let's call it question "b") is only displayed conditionally (ie: based on the answer to a previous question - let's call it question "a"), and a survey user answers that question (question "b"), but then moves backwards through the script and changes the previous question (question "a") such that this question (question "b") no longer displays, the survey will still remember and save their answer to the no longer applicable question (question "b"). I generally prefer this to be the case, on the basis that it may be interesting to know this information anyway. But, if you would prefer that the script be consistent and refuse to store information that shouldn't logically display you can change this setting to 1, and the script will not save this redundant information."

@Kai, please attach your survey and check that above setting.

TMSWhite

TMSWhite

2012-04-16 22:42

reporter   ~18398

$deletenonvalues is no longer used in LimeSurvey 1.92+. Irrelevant values are always NULLed in the database, regardless of the setting of $deletenonvalues.

This decision was to ensure that the database is internally consistent. Other strategies can be taken to keep track of the history of answers.

ResearchOnBlogs

ResearchOnBlogs

2012-04-16 22:56

reporter   ~18399

Hi Thomas,
I will make a test an Wednesday - I'll give you feedback

Mazi

Mazi

2012-04-16 23:10

updater   ~18400

Thanks for the hint, Tom. I updated the docs.

TMSWhite

TMSWhite

2012-05-02 04:56

reporter   ~18534

roB2009, any feedback? If we don't receive any, we'll mark this issue as closed.

ResearchOnBlogs

ResearchOnBlogs

2012-05-02 09:00

reporter   ~18535

hi Thomas,
take a look on my upload.

TMSWhite

TMSWhite

2012-05-02 13:30

reporter   ~18545

Seee note http://bugs.limesurvey.org/view.php?id=6004#c18344

The system is behaving exactly as intended. I confirmed that the proper values are saved in the database.

ResearchOnBlogs

ResearchOnBlogs

2012-05-02 15:47

reporter   ~18550

thanks

Issue History

Date Modified Username Field Change
2012-04-11 10:40 ResearchOnBlogs New Issue
2012-04-11 15:44 TMSWhite Note Added: 18317
2012-04-11 15:44 TMSWhite Status new => feedback
2012-04-12 15:42 TMSWhite Note Added: 18338
2012-04-13 04:45 TMSWhite Note Added: 18344
2012-04-16 22:37 Mazi Note Added: 18395
2012-04-16 22:42 TMSWhite Note Added: 18398
2012-04-16 22:56 ResearchOnBlogs Note Added: 18399
2012-04-16 22:56 ResearchOnBlogs Status feedback => new
2012-04-16 23:10 Mazi Note Added: 18400
2012-04-16 23:11 Mazi Assigned To => TMSWhite
2012-04-16 23:11 Mazi Status new => assigned
2012-05-02 04:56 TMSWhite Note Added: 18534
2012-05-02 08:59 ResearchOnBlogs File Added: limesurvey_survey_62766.lss
2012-05-02 09:00 ResearchOnBlogs Note Added: 18535
2012-05-02 13:30 TMSWhite Note Added: 18545
2012-05-02 13:30 TMSWhite Status assigned => resolved
2012-05-02 13:30 TMSWhite Fixed in Version => 1.92+
2012-05-02 13:30 TMSWhite Resolution open => no change required
2012-05-02 15:47 ResearchOnBlogs Note Added: 18550
2012-05-10 12:22 c_schmitz Status resolved => closed