View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|16255||Bug reports||Survey editing||public||2020-05-10 20:22||2021-03-10 17:42|
|Summary||16255: Editing "sub-questions" button is not visible.|
|Description||This is exactly what I was looking to know how to do.|
To be able to make a sub-answer and to see the sub-answers,
only if the user chooses the answer with the sub-answers.
By accident I saw this.
1. Clicked on the link from the "Data consistency check" number "1072" (image_2020-05-10_20-22-46.png).
2. It got me to "edit subquestions" place (image_2020-05-10_20-29-03.png).
Also saw an unknown-code (unknown-code.jpg) under the question that I wanted to make a sub-answer to.
I don't know what that code is or does.
|Tags||No tags attached.|
|Complete LimeSurvey version number (& build)||Version 4.2.1+200428|
|I will donate to the project if issue is resolved||No|
|Database & DB-Version||same|
|Server OS (if known)|
|Webserver software & version (if known)|
image_2020-05-10_20-22-46.png (193,681 bytes)
image_2020-05-10_20-29-03.png (164,818 bytes)
|This looks like LimeSurvey 3?|
|You mean maybe the code is a remain from before upgrading to LS4?|
|LS4 has no "Edit subquestions" button since they are edited at the bottom of the question editor. Maybe that's why you're confused?|
|So how do I get to see the "+" button so I'll be able to make a subanswer?|
|Ah, maybe there's a url to the old question editor still in LS4 that should be updated. You should go to survey overview and navigate from there instead.|
In the overview place didn't see any link in for showing the "+" sign.
overvioew - https://manual.limesurvey.org/Overview#Overview_toolbar
"+" sign - https://bugs.limesurvey.org/file_download.php?file_id=13178&type=bug
|@ollehar : see "Data consistency check" , related bug are maybe more clear|
|@ymca, could you please check LS 4.4.0 RC1 and see if the issue persits?|
we have asked for feedback on this issue. Because we did not get an answer we assume that the issue is resolved.
However, should you be able to reproduce the issue using the latest version, please feel free to re-open the issue and give us exact details on how to reproduce it.
Thank you and best regards,
|2020-05-10 20:22||ymca||New Issue|
|2020-05-10 20:22||ymca||File Added: image_2020-05-10_20-22-46.png|
|2020-05-10 20:22||ymca||File Added: image_2020-05-10_20-29-03.png|
|2020-05-10 20:22||ymca||File Added: unknown-code.jpg|
|2020-05-11 09:23||DenisChenu||Relationship added||related to 15798|
|2020-05-11 09:57||ollehar||Note Added: 57655|
|2020-05-11 10:12||ymca||Note Added: 57667|
|2020-05-11 10:19||ollehar||Note Added: 57669|
|2020-05-11 10:22||ymca||Note Added: 57671|
|2020-05-12 09:58||ollehar||Product Version||=> 4.2.1|
|2020-05-12 09:58||ollehar||Description Updated||View Revisions|
|2020-05-12 10:09||ollehar||Note Added: 57698|
|2020-05-12 14:46||ymca||Note Added: 57700|
|2020-05-12 15:58||DenisChenu||Note Added: 57702|
|2020-05-12 17:41||cdorin||Status||new => feedback|
|2020-05-14 16:49||ollehar||Priority||none => normal|
|2020-12-23 16:42||cdorin||Note Added: 61084|
|2021-03-10 17:42||ollehar||Assigned To||=> ollehar|
|2021-03-10 17:42||ollehar||Status||feedback => closed|
|2021-03-10 17:42||ollehar||Resolution||open => fixed|
|2021-03-10 17:42||ollehar||Note Added: 63103|