I think it's an documentation issue, it's an old survey, and using other in SUB QUESTION code can break Survey activation : see http://bugs.limesurvey.org/view.php?id=8514

ANd better we must fix this in model too (didn't allow it when importing)

Isn't only a documentation issue. How can I implement that EM solution (filtering array item + other option) if I cannot use the "other" string as sub-question/answer code? I think is better to find another keyword (permitted) for this case

I test when importing survey and add 'Other' option in Q2.

It's activated, but we have only one coluln for _other.

It work, but still not clean.

We don't allow other in javascript only, then you can unactivate javascript before submit again ....

I don't know if it's better to allow other or not. At first glance, i think we don't have to allow it in PHP too : because we can gather 2 information in one column, then we have another bug for this.

I agree to Denis. The 'other' option has been disallowed for several years now for the mentioned reasons. Obviously it did not bother too many people for array filtering so I vote for leaving it as it is.

@c_schmitz : maybe we just have to fix Question model then two ?