Is the core issue a problem with cascading array filters? I've fixed that known bug with Expression Manager (EM) so that multiple array filters work properly on the same and different pages.

I also updated the data model in the _CI and _dev_tms (to be 1.92) branches so that we can assign different relevance equations to each subquestion. That way, you can use a array_filter (which auto-creates sub-question-level relevance equations), plus add additional question and/or sub-question-level relevance (the successor for conditions). The Internal logic portions for that work, but we don't have a GUI yet for adding sub-question-level relevance, although that would be easy - just add an extra column in addition to code and/or assessment value.

Oups :
ideas.limesurvey.org/ideatorrent/idea/343/

Waiting moderation

Shnoulle wrote: Idea approved.

Mazi wrote: Comment added:
Using a question attribute is definitely the easiest solution to implement this. Simply add an attribute "CSS class name(s)" at which the user can enter specific class name(s) for a certain question. These must be added when generating the HTML code for the question at the survey (previouly done in qanda.php) and can then be used at template.css.

And another:

We should also look at automatically adding the question code to the question class.