Written by tpartner the 19 Dec 09 at 01:08.

To toggle the questions to optional, the button would query the DB, find all questions in the current survey with mandatory=Y and change them to mandatory=M.

We need to use "M" so we can find them to toggle them back later.

The system would see "M" as non-mandatory so all of these questions could now be skipped in a Q/A process.

This way only the questions that the survey author had set to mandatory would be affected.

To toggle the questions back to mandatory, the button would query the DB, find all questions in the current survey with mandatory=M and change them to mandatory=Y.

I've put together a little php script to demonstrate the concept that you can grab at http://partnersinc.biz/testsites/misc_images/mandatory_toggle.txt (can't seem to attach anything here!).

To toggle the questions to optional, the button would query the DB, find all questions in the current survey with mandatory=Y and change them to mandatory=M. We need to use "M" so we can find them to toggle them back later. The system would see "M" as non-mandatory so all of these questions could now be skipped in a Q/A process. This way only the questions that the survey author had set to mandatory would be affected. To toggle the questions back to mandatory, the button would query the DB, find all questions in the current survey with mandatory=M and change them to mandatory=Y. I've put together a little php script to demonstrate the concept that you can grab at http://partnersinc.biz/testsites/misc_images/mandatory_toggle.txt (can't seem to attach anything here!).

Written by tpartner the 19 Dec 09 at 14:40.

A more elegant solution may be to have the button/input set a session variable to disable the "checkmandatorys" function. (thanks Carsten)

Some red text could then be displayed at the bottom of the survey indicating that it is in "Q/A" mode and all questions are optional.

A more elegant solution may be to have the button/input set a session variable to disable the "checkmandatorys" function. (thanks Carsten) Some red text could then be displayed at the bottom of the survey indicating that it is in "Q/A" mode and all questions are optional.

Written by halliballi123 the 17 Oct 11 at 09:28.

add additonal field for input mask (like e.g. validation field)
if there is text in the field,

1 ) limesurvey has to add the script in the head of the html question page.

2 ) and set the alt tag of the input field to the mask

3 ) call setmask for the field

that's all

I also could imagine not just having a text field for the input mask, I could imagine having a drop down list of predefined masks of which I chose the one I want to use for the input field. like e.g. decimal or singed-decimal or german phone number format ...

but if there is a drop down that contains the list of input masks there also has to be a posibillity to edit those entries and add addtional input masks for the user.

add additonal field for input mask (like e.g. validation field) if there is text in the field, 1 ) limesurvey has to add the script in the head of the html question page. 2 ) and set the alt tag of the input field to the mask 3 ) call setmask for the field that's all I also could imagine not just having a text field for the input mask, I could imagine having a drop down list of predefined masks of which I chose the one I want to use for the input field. like e.g. decimal or singed-decimal or german phone number format ... but if there is a drop down that contains the list of input masks there also has to be a posibillity to edit those entries and add addtional input masks for the user.

Written by halliballi123 the 9 Aug 11 at 10:21.

- Button for saving (allready exists)

- Option for the creator of surveys for not needing username and password for saving and loading survey answers for surveys that are not anonymous.

After some discussions we found a working solution. It is already implemented, you just have to use the correct settings:

# Participant may save and resume later? = yes
# Enable token-based response persistence? = yes
# Anonymized responses? = no

- Button for saving (allready exists) - Option for the creator of surveys for not needing username and password for saving and loading survey answers for surveys that are not anonymous. After some discussions we found a working solution. It is already implemented, you just have to use the correct settings: # Participant may save and resume later? = yes # Enable token-based response persistence? = yes # Anonymized responses? = no

Written by lwc the 17 Nov 10 at 19:35.

Give the users a summary of all their answers, and force them to approve it in order to submit the survey.

Of course, make it an on/off option so each admin could decide whethere to force it or not.

Give the users a summary of all their answers, and force them to approve it in order to submit the survey. Of course, make it an on/off option so each admin could decide whethere to force it or not.

Written by andrewteg the 19 May 11 at 17:21.

Much like you have INSERTANS, I propose an INSERTQUESTION replacement field. Then you can at least setup a dynamic Question and Answer review page using a boilerplate field. This is not as convenient as a full review question page/type option, but would allow someone to setup a review page without having to retype the question text.

A quick button to spit out all of them would be pretty great too.

Much like you have INSERTANS, I propose an INSERTQUESTION replacement field. Then you can at least setup a dynamic Question and Answer review page using a boilerplate field. This is not as convenient as a full review question page/type option, but would allow someone to setup a review page without having to retype the question text. A quick button to spit out all of them would be pretty great too.

Written by Arthonas the 7 Apr 10 at 13:23.

As a possible solution the number fields should know the language used by the survey participant (variable) and interpret the number correctly.

As a possible solution the number fields should know the language used by the survey participant (variable) and interpret the number correctly.

Written by onderzoekspraktijk the 19 Nov 09 at 23:49.

Of-course more importantly it needs some coding of the used software. I tried it but it is beyond me.

Of-course more importantly it needs some coding of the used software. I tried it but it is beyond me.

Written by c_schmitz the 19 Oct 10 at 11:59.

Create a new setting to hide the Welcome page.
The end page problem will be resolved by conditioned text blocks.

Create a new setting to hide the Welcome page. The end page problem will be resolved by conditioned text blocks.

Written by lovepade the 3 Aug 10 at 08:59.

I think it would be a great service to e.g. send out a reminder email along the lines of (maybe only with token-based persistency):

"Dear NAME,

Our survey-system has registered that you on date begun to answer the questionaire - but you did not answer all the questions.

You can continue where you left of here: surveyurl

If you do not wish to continue, please press this link and we will not send you anymore reminder emails link.


This is an automatic email. You answers are anonymous, the system have only registred that you did not finish the querstions. Nobody - not even the systemadministrator, will ever know wether you finished the whole survey or not.

If you have any questions please contact surveyadmemail"

I think it would be a great service to e.g. send out a reminder email along the lines of (maybe only with token-based persistency): "Dear NAME, Our survey-system has registered that you on date begun to answer the questionaire - but you did not answer all the questions. You can continue where you left of here: surveyurl If you do not wish to continue, please press this link and we will not send you anymore reminder emails link. This is an automatic email. You answers are anonymous, the system have only registred that you did not finish the querstions. Nobody - not even the systemadministrator, will ever know wether you finished the whole survey or not. If you have any questions please contact surveyadmemail"

Written by apps the 2 Feb 10 at 10:06.

show_tics = 0 (default). Just as it is.
show_tics = 1 : the slider shows tics under the bar, between the slider_min and the slider_max values.

show_tics = 0 (default). Just as it is. show_tics = 1 : the slider shows tics under the bar, between the slider_min and the slider_max values.

Written by apps the 5 Feb 10 at 14:10.

Add a button to the survey button bar, next to "Token management"
Create a page to review all conditions in the current SurveyID

Add a button to the survey button bar, next to "Token management" Create a page to review all conditions in the current SurveyID

Written by Antongrau the 22 Jun 10 at 16:47.

A small feature would be a "Comment"/"Notes" button next the "Edit question" button. That button opens a window that lets you write a small note in plain text, that is attached to the question.

In the "Surveys" menu there could be a feature that gave you all the notes on one screen, with each question.

A better feature would be a "review" mode instead of a "test" mode. This feature would allow reviewers to add small comments (and view existing comments) when they test the survey.

The notes would of course not be visible when the survey was active.

A small feature would be a "Comment"/"Notes" button next the "Edit question" button. That button opens a window that lets you write a small note in plain text, that is attached to the question. In the "Surveys" menu there could be a feature that gave you all the notes on one screen, with each question. A better feature would be a "review" mode instead of a "test" mode. This feature would allow reviewers to add small comments (and view existing comments) when they test the survey. The notes would of course not be visible when the survey was active.

Written by Alfred_0825 the 3 Jun 10 at 18:54.

Put a search field in the answers like in tokens search.

Put a search field in the answers like in tokens search.

Written by wschatten the 25 May 10 at 21:28.

To do this successfully and easily in Limesurvey it would need to be something like this:
A new question type that is called RNG (random number generator).
The person creating the survey would be able to define the scale of the RNG, for example they would input '3' when setting up the question. And therefore the RNG would be between 1-3.

Every time the user encounters this question on the survey it would be a behind the scenes process that randomly generated a number instead of getting user input. The user would not be aware it happened nor see the number they were assigned.

Now the admin of the survey can set future question conditions on the RNG for this user.
For example all users who were assigned:
1 - will see a kitten
2 - a puppy
3 - a wolf eating a dead animal
followed by a question.

To measure the effects of the images on the user response it has to be randomized when the user takes the survey.

Adding in a RNG question type, to silently assign the user a number, allows the admin to easily define the scale of the RNG and also add multiple instances of it throughout the survey.

To do this successfully and easily in Limesurvey it would need to be something like this: A new question type that is called RNG (random number generator). The person creating the survey would be able to define the scale of the RNG, for example they would input '3' when setting up the question. And therefore the RNG would be between 1-3. Every time the user encounters this question on the survey it would be a behind the scenes process that randomly generated a number instead of getting user input. The user would not be aware it happened nor see the number they were assigned. Now the admin of the survey can set future question conditions on the RNG for this user. For example all users who were assigned: 1 - will see a kitten 2 - a puppy 3 - a wolf eating a dead animal followed by a question. To measure the effects of the images on the user response it has to be randomized when the user takes the survey. Adding in a RNG question type, to silently assign the user a number, allows the admin to easily define the scale of the RNG and also add multiple instances of it throughout the survey.

Written by tringate the 20 May 10 at 14:53.

Add a column in the survey list screen to give estimated survey table size.

The database type is known, and the estimated table sizes limits are known. A survey could be scanned and an estimated table size shown and those nearing the limits could be displayed in a different color.

Here is what the manual says about table size and unfortunatly after writting a very long survey and then trying to activate it I discovered I was way over the limit of what my database would accept.

...regarding survey size
Note: 'Survey size' refers to the maximmum number of questions (and answers) in your survey - don't confuse this with the number of replies on your survey (there is no limitation on that). Theoretically there would also be no limit on the maximum number of questions/answers in LimeSurvey. But the database engine you are using has several limits. The most important one is the limit on the number of fields(columns) in the result table.


•MySQL ISAM: The sum of the lengths of the VARCHAR and CHAR columns in a table may be up to 64KB.
•MySQL InnoDB: Maximum number of 1000 columns

Add a column in the survey list screen to give estimated survey table size. The database type is known, and the estimated table sizes limits are known. A survey could be scanned and an estimated table size shown and those nearing the limits could be displayed in a different color. Here is what the manual says about table size and unfortunatly after writting a very long survey and then trying to activate it I discovered I was way over the limit of what my database would accept. ...regarding survey size Note: 'Survey size' refers to the maximmum number of questions (and answers) in your survey - don't confuse this with the number of replies on your survey (there is no limitation on that). Theoretically there would also be no limit on the maximum number of questions/answers in LimeSurvey. But the database engine you are using has several limits. The most important one is the limit on the number of fields(columns) in the result table. •MySQL ISAM: The sum of the lengths of the VARCHAR and CHAR columns in a table may be up to 64KB. •MySQL InnoDB: Maximum number of 1000 columns •MS SQL Server 2000: Maximum number of 1024 columns •Postgres: Maximum number of 250-1600 columns depending on column types. The maximum number of columns can be quadrupled by increasing the default block size to 32k. See Installation FAQ and PostgreSQL FAQ. The mySQL ISAM engine is the most tricky one. As it allows only up to 65,535 bytes per row and utf8 characters can require up to three bytes per character the maximum may be only 21,844 characters (but this depends on your DB encoding). You can roughly calculate the size of your survey like this: •Every multiple numerical question: 20 chars for each answer •Every multiple choice & array question answers: 5 chars for each answer •Every other question type: 5 chars •Add 10% for the usual overhead

Written by mmaa the 18 May 10 at 18:49.

check each placeholder if it's empty and if so place a string like "no answer given"

check each placeholder if it's empty and if so place a string like "no answer given"

Written by m998dvd the 3 May 10 at 10:02.

It would be nice and handy, if there can be an extra column in this list and this next to "Total responses".

It would be easier to check and in one eye-view you see all the information that you needed.

"Full responses" > "Partial responses" > "Total responses" > "Total Requests".

Maybe one little thing after that requested column: "Percentage responded".

It would be nice and handy, if there can be an extra column in this list and this next to "Total responses". It would be easier to check and in one eye-view you see all the information that you needed. "Full responses" > "Partial responses" > "Total responses" > "Total Requests". Maybe one little thing after that requested column: "Percentage responded".

Written by Mazi the 23 Oct 09 at 16:24.

Solution for 1.
A) If $debug is set to "2"/"3" don't execute the mandatory check.
B) New config setting "$ignore_mandatory", if set to "1" don't execute the mandatory check.

Solution for 2.
A) Create a "All questions are mandatory?" -> yes/no option at survey settings
B) Create an overview which lists all questions and a simple "mandatory yes/no" radio option. This way you can set up your survey without making question mandatory from the beginning at chose which questions should be mandatory at a later step.
This overview can be survey or group based.

Solution for 1. A) If $debug is set to "2"/"3" don't execute the mandatory check. B) New config setting "$ignore_mandatory", if set to "1" don't execute the mandatory check. Solution for 2. A) Create a "All questions are mandatory?" -> yes/no option at survey settings B) Create an overview which lists all questions and a simple "mandatory yes/no" radio option. This way you can set up your survey without making question mandatory from the beginning at chose which questions should be mandatory at a later step. This overview can be survey or group based.

Written by GregB the 16 Feb 10 at 23:28.

It would seem to me that someone very smart person could make some script to convert survey data into mindmap data.

This would be a straight export from LimeSurvey to the mindmap data structure.

Branches can be colorcoded to denote conditions.

It would seem to me that someone very smart person could make some script to convert survey data into mindmap data. This would be a straight export from LimeSurvey to the mindmap data structure. Branches can be colorcoded to denote conditions.

Written by holch the 5 Mar 10 at 18:59.

I agree that the MindMap Structure wouldn't really work.

But I know some survey tools, that use a kind of "folder structure" as we know it from file explorers, etc.

I think this can display filters and so on pretty well. At the moment Quotas, Filters, and questions are somehow displayed very seperate and it difficult to get a good overview of the survey (I do agree with the GregB here).

But with the folder tree, you can show loops, filters, pages/groups and questions, which can be especially helpful for long and complicated surveys.

I agree that the MindMap Structure wouldn't really work. But I know some survey tools, that use a kind of "folder structure" as we know it from file explorers, etc. I think this can display filters and so on pretty well. At the moment Quotas, Filters, and questions are somehow displayed very seperate and it difficult to get a good overview of the survey (I do agree with the GregB here). But with the folder tree, you can show loops, filters, pages/groups and questions, which can be especially helpful for long and complicated surveys.

Written by leolime the 6 Feb 10 at 19:09.

To have a button same as the Question Preview a Question Group Preview-Button.

To have a button same as the Question Preview a Question Group Preview-Button.

Written by apps the 5 Feb 10 at 16:12.

The use case can be safely split in 2 use cases, by looking at the level of interaction the user need with the settings.

A "survey messages" +
A "survey settings " (Retain old name)

The use case can be safely split in 2 use cases, by looking at the level of interaction the user need with the settings. A "survey messages" + A "survey settings " (Retain old name)