Personally, I'd vote to going back to the way 1.91+ worked. I have plenty of surveys where users want to check the other check-box, but do not be forced to specify any details. The changed implementation does not allow that.

The that caused the current behavior was made by Denis about a month ago.

Yeah, or maybe have an option "Hide Other checkbox".

TMSWhite écrit: This would also be my preferred solution as default behavior. Maybe we can then have a second behavior which is triggered by an advanced question setting.

Dear Tony - many thanks for the prompt and detailed help. Worked like a charm. It wasn't immediately obvious what the question code was for my 'other' option but worked it out from the survey logic file.

Cheers,
Glen

Hi tpartner,

I encountered the same issue and I tried to use your solution. But the system does not let me use code "other" for Question 2. It gave me a error warning which is "Error: other is a reserved key word". I believe I am using 1.92 version. Any solution for that?

Thank you in advance!

I have just tested the solution with the latest release of 1.92 and it allowed me to use "other" as a sub-question code in a multiple-numeric question and the filtering and piping worked.

Please update to the final release of 1.92 and retest.

I just checked that our version is "LimeSurvey Version 2.00+ Build 121127".

I tested again it will let me put in code "Other" not "other". But if it is "Other" it looks like a new code has nothing to do with the one from previous question. Here are my screenshot.

Oh, yeah, in 2.0 you can't use that code which I still consider to be a bug. See this post for more discussion and a possible solution - www.limesurvey.org/en/forum/design-issue...-cascade-array#88753