In the pluguin : knowVars is set here : https://gitlab.com/SondagesPro/coreAndTools/organizeSurvey/-/blob/master/organizeSurvey.php#L93-96

@ollehar :
3 solutions :

1. Add questionSeq2relevance to the event set and get
2. Set questionSeq2relevance as public (but it's in session)
3. Move questionSeq2relevance setting after the event : reread knowVars

Tell me what solution can be accepted in master , if not in develop.

@ollehar : i think of a 4th solution.

1. Create some public function in EM
   1. setQuestionHidden($qid,$hidden = true);
   2. setQuestionrelevance($qid,$relevance);
   3. getQuestionHidden($qid);
   4. getQuestionrelevance($qid);
2. Add related function in API
   1. ExpressionProcessStepString (have one currently but broken)
   2. ExpressionSetValueToKnowVar : used by expressionFixedDbVar
   3. ExpressionUpdateReplacementFields
   4. ExpressionSetQuestionHidden
   5. ExpressionSetQuestionrelevance
   6. ExpressionGetQuestionHidden
   7. ExpressionGetQuestionrelevance

Are you OK with such pull request principle ?

For my current project : i need a way to update relevance or hidden dynamically.

But i think a "Hidden by expression" can be really great
https://bugs.limesurvey.org/view.php?id=13835

With API n: no way to "Set order od question by ººº"

We have random, but i have a system where they use "Order by token attribute" (and hide some by token attribute".
LimeSurvey 1.80 hacked version + 1.92 + .... never find a way to get it in a clean way.

Add questionSeq2relevance to the event set and get : https://github.com/LimeSurvey/LimeSurvey/pull/1392

• Advantage : the most par updatable by plugin, no need other. I'm sure we can set order etc ...
• Con : plugin s can broke totally Expression Script system easily

Add related function in API

• Advantage : ? Unsure
• Con : Create new function in EM just for API. API just call just created function

Please tell me your preference.

https://github.com/LimeSurvey/LimeSurvey/pull/1392 is the easiest, already checked for hidden. But ... allow a lot by plugin.

Extend API seems more a false bad idea.

I try «Move questionSeq2relevance setting after the event : reread knowVars » but this was too complex... Maybe update questionSeq2relevance partially with the new knowVars only ?
But we loose order of questions by plugins.

Forum post where a plugin ca be interesting Grouping questions within a question group

@ollehar : develop branch are 4.0.0dev ?

@ollehar : develop branch are 4.0.0dev ?

No, should be 4.x.0-dev, I guess.

Then must create a 4.X-dev :)

Blubb. One sec.

Done.

:+1:

fixed in 4.4.0 rc1