Hi, I'm new to LimeSurvey and we're having trouble finding a way to prevent that, once we have, say, 150 respondents, the questionnaire to keep accepting new entries. We'd like to redirect LimeSurvey, once we've achieved the referred quota, to another page.

I've seen this question here somewhere, but could not find a suitable answer.

Thanks

I think this is a tricky one. You basically would need to create a question with just one answer I guess. Then you could set a quota on this. I am not aware of a way to close a survey when it has reached a certain number of total completes.

Would be a good feature I think.

I have the same problem! A way to close a survey when it has reached the quota would be a good feature!

Well, I think it would be good to make a feature request in the bug tracker and link it here, so everyone can vote for it, so chances get higher it will be implemented.

I think you can use a "single choice" hidden question with default set to "quota".
Put this question in first group (only one question) and set quota to this question.
Then when user click next at welcome page is go to quota

Good suggestion Denis but I can still see the value in having a "Maximum Responses" setting in the Publication & access control tab.

tpartner wrote: Good suggestion Denis but I can still see the value in having a "Maximum Responses" setting in the Publication & access control tab.

Hi Tony,

A plugin idea ?

I think it's easy to use beforeSurveyPage to :
- Test if srid is set : if not : test number of "completed?" response
- If completed responses >= "survey plugin setting" : show a message, and don't start survey.

We can test to without testing srid : and break the survey during response time.

Not so difficult to do survey : one day of work.

Denis

You can add this to this feature request:
www.limesurvey.org/en/forum/future-featu...tallation-per-survey

There are many scenarios where a temporary stop is needed.
When the specs are clear, I would like to try a bounty/feature sponsoring.
Since two programmers where hired by the project, I am not sure if the bounty discussion will be fruitful anymore.
Not sure how sponsored features will work. Would a bounty of e.g. 250 EUR do more harm than good? Is a certain amount devaluating the work of a programmer?

I am not sure if this shouldn't be a core feature rather than a plugin. This is clearly something the survey engine itself should handle, I think. But then I am not a developer.

holch wrote: I am not sure if this shouldn't be a core feature rather than a plugin. This is clearly something the survey engine itself should handle, I think. But then I am not a developer.

The question is, whom will maintain these plugins. If they are packaged with Limesurvey and maintained by the core developers it might work.
If these plugins are at risk with every update of the core distribution and have to be downloaded and activated by hand it will be DOA.

A plugin is more quick to update and fix according to core.

A plugin are not removed when update

Core have bug with less used option .....

Thanks, holch!

Submitted as a feature: bugs.limesurvey.org/view.php?id=9816
Thanks all!

holch wrote: I am not sure if this shouldn't be a core feature rather than a plugin. This is clearly something the survey engine itself should handle, I think. But then I am not a developer.

I strongly vote for making this a core feature. Plugins are nice for very special stuff but closing a survey once X completed responses were collected is a common approach at market research surveys.

It depends on the way plugins are shipped and tested. When we read the name "plugins" it can come in different forms. In Joomla there are plugins, which are always shipped with the core installation and always activated. The difference is only visible for the programmer, which needs to use a API.

When plugins means, that users need to download them and activate them, then I see a lot less testing of these features. When we look at 2.06+ with all its regressions it might be useful to encapsulate more code.
Currently 2.06+ isn't stable. The bugtracker shows a clear picture. With plugins the debugging can be quicker, because code parts can be easily switched on and off (at least for the programmer). I would suggest to get the wording and the concept clear. I would suggest to introduce coreplugins as name, for functions, which are plugins, but will be shipped activated with the core installation.