Hi Joffm. There has been some discussion about this but, as far as I know, it is still not available in Expression Manager.

Unfortunately, somehow the question text is not accessible for questions with subquestions. I don't understand why, but it is what it is. I think I have even created a bug report or feature request at one point. But I don't think that this every moved forward. Seems like no one wants to touch Expression Manager...

holch wrote: Seems like no one wants to touch Expression Manager...

Seems to be this "feature" request:
bugs.limesurvey.org/view.php?id=8858

.question in IF broken.
bugs.limesurvey.org/view.php?id=14486

Looks like more lipstick on a pig (e.g. WYSIWYG Mode) first.
As long as I see tweets stating that LimeSurvey is as powerful as Qualtrics, the strategy seems to be right.

Yes, it is what it is.

And it is not a big concern. But I just wanted to ask, in case I missed something somewhere.

Joffm

yeah, I was as suprised as you were when I noticed this the first time. Wasn't a big deal for me at the time as well, but I can see how it can be a lot of extra work in some specific cases.

holch wrote: …
I don't understand why, but it is what it is.
…

Expression Manager use variables and fixed string.

Variables are the answer of question : the part filling the database. Single quuestion : Q1 is the variable, multiple question Q1_SQ1 is the variable : see www.limesurvey.org/manual/Expression_Man...code_Variable_Naming

Fixed string are TEMPLATEURL, SID, TOKEN:XXXX etc …

When know this : the question is why we have Q1.question ? It's more a hack, and helper than something logic


Q1 in a multiple question didn't get in variable .

You can think it's easy to have Q1.question : the question of Q1 BUt : what for Q1.NAOK ? Q1.value ? Etc …

It's the reason.

I don't think we would need anything else than "Q1.question" and it is the only thing that makes sense.

holch wrote: I don't think we would need anything else than "Q1.question" and it is the only thing that makes sense.

Yes : but then Expression manager muts be totally rewritten from scratch …

I think about a way to update knowVars by plugins to fix this issue (adding a plugin in core) : adding Q1.question for multiple choice and adding Q1.help for all question

But i'm unsure of the best way …

1. Easy way : allow adding only «fixed» string like today (the most easy)
Then : QUESTION_Q1,QUESTION_Q1_SQ1 etc … but what happen if there are QUESTION in survey
2. Allow update variable part : then have Q1.question and Q1.help : think it's great but can broke a lot of things …
3. Only allow new fixed variable without _ (only alphabetic) : easiest but … lack of feature
4. Only allow new fixed var + create own part QUESTION:Q1, QUESTION:Q1_SQ01 (like token) : think it's the cleaner but did we have all feature needed ?

Discussion here : www.limesurvey.org/forum/development/118...te-by-plugins#182458

Yes : but then Expression Manager muts be totally rewritten from scratch …

I know. But I also know that everyone is scared of that. So it will most probably never happen.

I met the same issue.
Is there still no workaround?

No workaround,

In project (by core plugins) in 4.0 : github.com/LimeSurvey/LimeSurvey/pull/1256

Nope. As long there hasn't appeared a sponsor with big pockets to finance the rewrite of Expression Manager, the situation is still the same.

holch wrote: Nope. As long there hasn't appeared a sponsor with big pockets to finance the rewrite of Expression Manager, the situation is still the same.

DenisChenu wrote: No workaround,

In project (by core plugins) in 4.0 : github.com/LimeSurvey/LimeSurvey/pull/1256

This was not sponsored , doing it for glory …

This was not sponsored , doing it for glory …

i was more referring to the complete rewrite of EM, that you said was necessary to include this.

Nice to see that this will be possible in LS 4.