|Dependency Graph||View Issue Relation Graph Vertical|
View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|08858||Feature requests||[All Projects] Expression Manager||public||2014-03-14 11:16||2019-08-14 09:01|
|Target Version||Fixed in Version||4.0.0dev|
|Summary||08858: Extend EM so we can get the question text of multiple choice and array questions via questioncode.question|
For multiple choice questions or other questions using subquestions the syntax "questioncode.question" is currently treatd as invalid and one only seem to be able to get the subquestion text via questioncode_subquestioncode.question.
Currently there is no possibility to also retrieve the question text for these question types.
mfaber, I assign this to you since you now seem to know EM inside out and thus I am interested in your opinion if this is hard to implement.
|Tags||No tags attached.|
This make a lot of change in EM : core and manager
Not in 2.05, but more for 2.06
And allow access to other information too (get from DB, and not from session :help is the first example).
For questions with subquestion this may actually qualify as a bug (missing implementation)....
Carsten, please advise:
This is our status:
For questions without subquestions (eg. single answer)
For questions with subquestions (eg. matrix)
Problem is that only subquestions are in the fieldmap and other data structures, so for a matrix question, QCODE without a subquestion code is (for EM) not a valid variable. And i am reluctant to change that only because we would like to access "QCODE.question".
What can be very easily implemented is an additional question attribute (let's call it ".questiontext"?). So the main questiontext of a matrix question could be accessed with QCODE_ANYSQCODE.questiontext. Question is: Would that be ok/helpful? Or rather leave it as it is?
Tom, do you have any advice for us how to best deal with this?
Like mafaber say, 2 siolution:
Very difficult to choose, because after choosing, it can be more easy or more difficult to add a new system (question-help is one example, but our user have surely a lot of idea).
Carsten: feel free to assign this back to me if you think a ".questiontext" attribute would be helpful (see http://bugs.limesurvey.org/view.php?id=8858#c29532)
If I can add that this is a problem for me. When creating a "Review page" subquestion answers without the main question context can be meaningless. In the survey I am currently working on I need to display an image which is embedded within the question text to give the answer some relevance.
I can work around it but its a lot more complex than one would hope.
Why not a new event (or 2 news events)
About EM : the danger is whole system goes in $_SESSION , then it already make a big SESSION part .....
I can see how this might be very difficult.
You also have the problem of if a question itself references a previous question and then you reference the dependent question, will the expression manager handle it correctly. As I do not know how the expression manager works (its magic isn't it) I do not know how complex this problem may be.
If you activate expressionQuestionHelp you have Q00.help too \o/
@DenisChenu, I know you prefer adding functionality as plugins but isn't this some core feature to be able to properly get the question text by an EM placeholder?
@c_schmitz, what do you think? My suggestion would be adding this fix to the core code. Alternatively, add it as an activated core plugin.
@Mazi : here one fix for 3 plugins (in core, distributed with core).
And more : Expression Manager SESSION is already big. Some user already have issue with big session, the this QCODE.question MUST be optional because it fill again the SESSION …
I really think core must not add always something in SESSION (+ in PHP memory and time) if it's rarely used …
|2014-03-14 11:16||Mazi||New Issue|
|2014-03-14 11:16||Mazi||Status||new => assigned|
|2014-03-14 11:16||Mazi||Assigned To||=> mfaber|
|2014-03-14 11:45||DenisChenu||Note Added: 29261|
|2014-03-14 11:46||DenisChenu||Note Edited: 29261||View Revisions|
|2014-03-14 14:48||Mazi||Relationship added||related to 08859|
|2014-03-17 22:34||mfaber||Note Added: 29306|
|2014-03-25 22:28||mfaber||Note Added: 29532|
|2014-03-26 09:41||Mazi||Note Added: 29533|
|2014-03-26 09:57||DenisChenu||Note Added: 29534|
|2014-05-02 11:08||mfaber||Assigned To||mfaber => c_schmitz|
|2014-05-02 11:10||mfaber||Note Added: 29925|
|2017-02-14 04:52||DeveloperChris||Note Added: 43007|
|2017-02-14 09:38||DenisChenu||Note Added: 43008|
|2017-02-15 00:25||DeveloperChris||Note Added: 43013|
|2019-07-24 20:37||DenisChenu||Note Added: 52992|
|2019-07-24 20:37||DenisChenu||Assigned To||c_schmitz => DenisChenu|
|2019-07-25 09:51||Mazi||Note Added: 52996|
|2019-07-25 10:14||DenisChenu||Note Added: 52997|
|2019-08-05 16:29||DenisChenu||Status||assigned => resolved|
|2019-08-05 16:29||DenisChenu||Resolution||open => fixed|
|2019-08-05 16:29||DenisChenu||Note Added: 53113|
|2019-08-05 16:30||DenisChenu||Status||resolved => feedback|
|2019-08-05 16:30||DenisChenu||Resolution||fixed => reopened|
|2019-08-05 16:30||DenisChenu||Fixed in Version||=> 4.0.0dev|
|2019-08-05 16:30||DenisChenu||Status||feedback => resolved|
|2019-08-14 09:01||Mazi||Relationship added||related to 14200|