soon subquestions editing will directly in question edit.

That's good to know

I can't wait for it! (I assume it will cover sub questions and answer options though?).

Features missing?

* Allow users to resubmit (change his vote) again and again, every X days (after 1 month from last voting submission) or only once (not for a question like user birth-date).
* Automatic "Question code" fill.

Question code: Your ID, or number or code for the question. This field is only for quick identification for a question in export or for evaluation.

What feature is unique to Limesurvey?
-Limesurvey is free.
-You can use it without internet connection.
-You can do a LOT with javascript.
-LSA and LSS files are easy to edit.

What feature is missing the most?

first wrote: #Ability to get quota counts in survey. (Yes! So sad that we cant make "soft" quotas)
#Implementation of screen-outs without hacks. (Yes! Currently we should make a lot of quotas with quota limit=0 and sometimes 2 hidden questions for that quotas: equation + any single choice)
#Multiple Other specify in any question without hacks
#Page objects so that we can place more than one question on a page even in question by question layout. (Yes! Sub groups, page objects etc. At least a dirty hack like: if group name contain "magic" string questions from that group will be shown like in question by question mode)
#We are not able to use programming language loops (for,while,do while) in equation type question.

-Its hard to change default screens like "wrong token".
-More logs. "User XXX changed question YYY in survey ZZZ at TTT". And more userfriendly access to that logs.

What i dont like?
-Question's text cached after survey begining.
-Its pain when you need to show 49 questions on 49 screens and last 2 questions should be on the same screen.

in additional: i missing custom variables in the expression manager.

They can be separated from answers. We have tokens with syntax like TOKEN:ATTRIBUTE_1. How about variables with VAR:VARIABLE_NAME usage? We need counters sometime.

For example that expression in the equation question can check 3 previous questions with one variable:

I don't get it, where would this variables come from? What are these variables?

holch wrote: I don't get it, where would this variables come from? What are these variables?

They don't exist its feature that i like to see in limesurvey.

Yes, I understand that. But what would be the different to using a custom token attribute TOKEN:ATTRIBUTE_1 which could be anything, compared to your VAR?

holch wrote: Yes, I understand that. But what would be the different to using a custom token attribute TOKEN:ATTRIBUTE_1 which could be anything, compared to your VAR?

You cannot modify token attributes. And i know that i can use count() in my example but variables make life easier in many ways. I do not insist that their use should look exactly as it is, it's just an idea for LS 3.0+

About VAR: feature (and TOKEN:) feature.

I already think EM can be expandable by a way : something like this {PLUGINNAME:VARIABLE} or (maybe SESSIONARRAYNAME:VARIABLE, because TOKEN is a session var name).

It's just an idea

We just started to use LimeSurvey to enable customers to build up their own surveys.
LimeSurvey is a nice tool to manage surveys, it is easy to handle, so nearly everyone can build a survey.
It is responsive, you can use templates to give all surveys the matching CD.

but one big feature is missing and propably this will kick out LimeSurvey: There is no role-concept for admins. you have to set individual rights on individual basis (the user groups are only shortcuts for individual assignments).
Also it is very difficult to restrict access to the admin backend with an additional security layer like htaccess.

Another option we miss: export and import a survey (or template) with all belonging files (images, JS, CSS, ...) in one step/file.
Especially as our admin does not grant access by ssh/ftp to the server.

About Permission : it's extandable, you can do 'What do you want for Permission" www.limesurvey.org/manual/BeforeHasPermission
It's really the most easy Plugin Event here.

About survey (or template) with all belonging files : teplate can be already export/import, and look at survey ressource to export/import survey files.