We don't have a FR for array_filter ?

More for 2.5 or 3.0 than 2.06 i think
PS: did you try count(that.relevanceStatus) for relevance equation ?

Denis, I tested several different approaches using COUNT or SUM and SELF or THAT but none worked.

Seems self.relevanceStatus is javascript OK, but not relevance OK ...

I'm silly :

QQ_Subq.relevanceStatus == (QQ_Subq.relevance && QQ.relevanceStus)

Buggy here ... with relevanceStatus ....

Can be done in event.

But : template related ? Adding it in a new function OR core related : adding it in existing function.

Start by adding it to template

... Only for 'view'/css/js : not for PHP.

Touch this is more complex in EM

Fix committed to answers_html branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=21299

Fixed in js in default template . Reopen for PHP/QUestion by question mode (or only one question in such group).

Is linked with another issue : .relevanceStaus for sub question + .relevance must give direct equation relevance (not group.relevance && question.relevance if i remind).

"Reopen for PHP/QUestion by question mode"

I bet it's going to be pretty hard. Do you yet have any idea about how to proceed?

@LouisGac : yes.
1st : Create or look at QCODE_SQ1.relevance for subquestion : think it was broken actually (return NaN for subquestion)
2st : we must have a .relevanceEquation : return the equation for 'all' sub question

When we have it:
Find where to put :
Question.relevance = Question.relevanceEquation AND count (self.relevanceEquation) > 0.

Need a lot of work and testing

I think this could be useful, in SurveyRuntimeHelper:

if (isset($moveResult)){
$_SESSION[$LEMsessid]['step'] = $moveResult['seq'] + 1; // step is index base 1?

        }

@LouiGac : linked with this feature ?

If i remind step is 0 indexed, and -1 is for "welcome page"

PS : about this issue :
WWe can "easily" add the expression :
count(QCODE_SQ001.relevanceEquation,....) > 0

But really : i don't think we must show it in Expresssion Manager file.

An alterantive solution can be :

• Test if previewMode is set and is ==='logic'
  => Add the test only if we are not in "survey logic file system"
  (or export, or .....)

See https://github.com/LimeSurvey/LimeSurvey/blob/master/application/helpers/expressions/em_manager_helper.php#L66
and
https://github.com/LimeSurvey/LimeSurvey/blob/master/application/helpers/expressions/em_manager_helper.php#L9165

@LouisGac maybe i can take a look next week : you work on twig next week ? If yes : i give it a try (working on EM mmmm !)

Is that issue fixed / feature added?

Currently : done for javascript in develop for default template : https://github.com/LimeSurvey/LimeSurvey/blob/develop/application/core/packages/template-default/template-core.js#L95

Really more hard to have a clean way in EM currently (relevanceStatus and relevance is broken)

ANd : if it's not set 'fixed' => it's not fixed

this bug will be very easy to fix in the twig, so I suggest to leave it as it is in 2.50.
see:

https://github.com/LimeSurvey/LimeSurvey/blob/twig-layout/templates/default/views/question.twig

Easy to fix in HTML : OK : "fix it if there other question in same page" .

BUT : this don't fix question by question mode .... if you have a question with all subquestion hidden : the 'step' still valid.

Current develop default template fix it too ....

well, that's should be a fix in the next step calculation.

<autoquote> Touch this is more complex in EM </autoquote> and step are managed by EM currently

something like this:

in SurveyRuntime Helper, here:
https://github.com/LimeSurvey/LimeSurvey/blob/twig-layout/application/helpers/SurveyRuntimeHelper.php#L1012

if ( question by question mode && all subquestion hidde )
LimeExpressionManager::JumpTo($_SESSION[$LEMsessid]['totalsteps'] + 1, false)

Denis: I've just seen your comment about EM. I trend to consider SurveyRuntime as a controller and EM as a model.
That's why I think those kind of calculations should rather be in SurveyRuntime.

To be more accurate, I bet that piece of pseudo code should work:

Right now we have:
https://github.com/LimeSurvey/LimeSurvey/blob/twig-layout/application/helpers/SurveyRuntimeHelper.php#L1011-L1013

        if ( $move == "movenext"){
            $moveResult = $this->moveResult = LimeExpressionManager::NavigateForwards();
        }

I think we should have:

        if ( $move == "movenext"){
            if ( question by question mode && all subquestion hidde ){
                $moveResult = $this->moveResult = LimeExpressionManager::JumpTo($_SESSION[$LEMsessid]['totalsteps'] + 1, false);
            }else{
                $moveResult = $this->moveResult = LimeExpressionManager::NavigateForwards();
            }
        }

Still relevant for LS 3.X? Subquestion relevance and array filter can end with everything hide.

@jelo : template-core.js have a solution for this. The real only issue (must) be in question by question mode.

I put must because : not tested since 3.X (not RC) release mean not really fixed (a lot of update are done in HTML and JS after answers_html work)