Well, I don't have an answer - it's gotta be a bug.

The bad news is that there are no more bug fixes for LS 2.0. The good news is that it only happens when reviewing the group, not when executing the survey.


.

Yes, the good news is it does not affect the execution! It is merely annoying when trying to get a sense of design and feel for the user experience of that section. Now I will go and find out if I add another group if the behaviour promugates or is confined to just the second group. I'll get back to you on that ASAP and then we can close this discussion I guess.


ETA: Nope, doesn't promulgate to a newly created group. It is specific to just that second group.

So, Now I will leave you with the conundrum (sorry 'bout that!) and thank you formally for your time (I appreciate it very much) and i will decide whether it is worth my while recreating the group as new or to just live with the inconvenience...

Is there a way of the poster marking a post to indicate that the issue has been resolved / not resolved but still concluded / not solved action still required (or similar) ?

More information:

I created a whole new section (group 2 made from scratch). It previewed and tested perfectly. Then I deleted the existing group 2 (ostensibly the one with the bug in it) and re-ordered the new group into the old gropup 2 position. Then the bug reappeared!!! So it has something to do with the POSITION - not the content -no matter what is in that position - it will have the bug in it.

I know you say there are to be no more bug fixes for LimeSurvey version 2 ...but you will need to fix it in the next version surely?

Really strange issue ...

Can you provide the lss file example or a link to the survey ?

Denis
PS: your LimeSurvey version please .

Hi Denis, the group is attached above and I can reproduce the problem on 2.0 - 131206.

Hi again - More info...

I have added some conditions to three of the questions in the group (visible only if the first equals yes) and the behaviour of the group is just what it should be in test mode (even when it is either the first question that is missed or one of the questions with the conditions or any other question or multiples thereof). In other words, the bug in group 2 position's preview mode that creates the "This question is mandatory" text does not seem to affect how the survey acts or reacts under test conditions (and hopefully won't when we go live).

Thankfully then it does not seem to be a fatal bug, however, that being stated, there was one test I did that proved fatal for the survey (when the initial question was missed) - and that was the first test after I recreated, deleted and repositioned (as in my previous post). The survey got stuck in a "This question is mandatory" loop and no matter what I selected or deselected in that group 2, it would not move on - and I was forced to close the survey altogether . However I cannot repoduce that behaviour and after that little scary moment all seems fine ...

I have the same issue with Version 2.67.3 and happens when previewed or when executed. For me this happens on the Conditional fields - when backward Navigation is enabled.

MadhuraBL wrote: I have the same issue with Version 2.67.3 and happens when previewed or when executed. For me this happens on the Conditional fields - when backward Navigation is enabled.

Since it's a 4 years old topic with a pre 2.6lts template : you must create a new topic.

I close this one