Check out the LimeSurvey source code on GitHub!

Make question idx NOT red when section has array (numbers) check box question?

More
3 years 3 months ago #100633 by w0928
By default, the labels for each section listed in the question index are red when a section contains questions that have not be answered.

I've noticed though, that for my sections which have an array (numbers) question with checkbox style set to yes that those section are always red... even when at least 1 column has been checked for every row for the question.

So my question is, what conditions must be satisfied for the question index to count such questions as having been completed by the user and how would I go about changing that?

Please Log in to join the conversation.

More
3 years 3 months ago - 3 years 3 months ago #100706 by w0928
I found this in the bugs section. It is marked as fixed but I am having the same issue so maybe this was not quite fixed?

bugs.limesurvey.org/view.php?id=5323

Edit: I'm using version 2.00+ (build 130802) Aug 2, 2013.
Last Edit: 3 years 3 months ago by w0928.

Please Log in to join the conversation.

More
3 years 3 months ago - 3 years 3 months ago #101014 by w0928
I have a little more info to provide on this issue. I noticed that in cases where the question index was red and the user submits the survey the checkboxes that are left unchecked are being saved to the database as null and in the case where it is not red the checkboxes that are left unchecked are being saved as 0.

I would really appreciate it if a developer would comment on this issue. Is this working as intended? What is causing the discrepancy for the question index coloring and the values that get saved? They appear to correlate with one another.

Thank you.
Last Edit: 3 years 3 months ago by w0928.

Please Log in to join the conversation.

More
3 years 2 months ago #101018 by w0928
More info: the missing class is being added to the array numbers question just like it was reported in this bug report:

bugs.limesurvey.org/print_bug_page.php?bug_id=5323

Maybe the bug crept its way back in?

Please Log in to join the conversation.

Imprint                   Privacy policy         General Terms & Conditions         Revocation information and revocation form