Sometimes I get a question about how to add file upload for a survey.
I think that "Mask question" is not good. Could we 1) add new category "Pseudo questions", 2) move Equation and Text display to it, 3) Rename Mask question to Other question types", and 4) move Multiple numerical input to Arrays-category?
And when we are on it, change the order of categories so that Multiple choise questions would be after Single choise questions, Arrays after then.
Last, to native English speakers: Why we have Language switch but Numerical Input, why this kind of uppercasing?
(I can make a bug report, but I want first to see if others are against this.)
Review all Question categories seesm to be a good idea ! Right totally right !
4 : Multiple numerical input to array ? No , think «Multiple numerical input» «Multiple text» «Multiple with comment» are near each other.
Another thing : QuestionTheme can update the category too ?
(+1 for the little issue about uppercase)
Assistance on LimeSurvey forum and LimeSurvey core development are on my free time.
I'm not a LimeSurvey GmbH member. -
Professional support
-
Plugins, theme and development
. I don't answer to private message.
I agree that the categorization of the question types is really not ideal. Also, "hiding" certain "question types" in settings of other questions is also not a good practice, because people usually won't search for this "type of question" in another question type.
But these are all things that grew historically and were never really tackled strategically or from a usability point of view. Unfortunately the interface is usually done by developers, which often actually do not even really use Limesurvey for projects.
Help us to help you!
Provide your LS version and where it is installed (own server, uni/employer, SaaS hosting, etc.).
Always provide a LSS file (not LSQ or LSG).
Note: I answer at this forum in my spare time, I'm not a LimeSurvey GmbH employee.
Last edit: 3 years 7 months ago by holch.
The following user(s) said Thank You: DenisChenu, Jmantysalo
Thank you for reporting this issue. I have created a task and it has been placed in the product backlog, with other UI improvements which we are currently fixing.