Written by luc_dubois the 16 Mar 10 at 05:22.

A way to prevent this is to hide the completed field and have a reset button instead if you want to ask the user to do the survey again. That's in the token management screen.

This condition could be only for anonymous survey.

That way, i don't know who has completed the survey and now it's more anonymous.

And been myself a little paranoid regarding security, I would encrypt the completed field in the lime_token table so a administrator with mySql skill could not see the result via PhPAdmin

A way to prevent this is to hide the completed field and have a reset button instead if you want to ask the user to do the survey again. That's in the token management screen. This condition could be only for anonymous survey. That way, i don't know who has completed the survey and now it's more anonymous. And been myself a little paranoid regarding security, I would encrypt the completed field in the lime_token table so a administrator with mySql skill could not see the result via PhPAdmin

Written by Morpheus the 27 Jul 10 at 12:34.

Great would be if the user could pick an ole-db provider to connect the dbms of his choice.

When the dbms is chosen LimeSurvey would have to provide campaigns which should be subdivided into different data groups (e.g. data group A represent people of zipcode 1, data group B represent people of zipcode 2 and so on).

Within one data group you can limit the data amount by just selecting specific records with a sql command of the specified data source

Each data group should be limited to a specific response quote for a specific question.

Great would be if the user could pick an ole-db provider to connect the dbms of his choice. When the dbms is chosen LimeSurvey would have to provide campaigns which should be subdivided into different data groups (e.g. data group A represent people of zipcode 1, data group B represent people of zipcode 2 and so on). Within one data group you can limit the data amount by just selecting specific records with a sql command of the specified data source Each data group should be limited to a specific response quote for a specific question.

Written by tacman1123 the 5 Feb 12 at 13:06.

When tokens are defined, instead of merely asking "how many", it would need to change to a list format that asked the field names (and types, but that's a different issue!)

When tokens are defined, instead of merely asking "how many", it would need to change to a list format that asked the field names (and types, but that's a different issue!)

Written by freddekkers the 14 Dec 09 at 12:37.

Make it possible to make a butten with a link to [serveyurl] when editing invitation/reminder e-mail (in fckeditor).

Make it possible to make a butten with a link to [serveyurl] when editing invitation/reminder e-mail (in fckeditor).

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

PHPList is an open source newsletter package that I use to keep in touch with my subscribers.

It has an email queue that automatically works through batches of emails until it has sent all them all. The email queue can process automatically using cron jobs.

Since PhPList is open source and LimeSurvey is open source, maybe PHPList would share some lessons learned and allow sharing of some of theri current code?

PHPList is an open source newsletter package that I use to keep in touch with my subscribers. It has an email queue that automatically works through batches of emails until it has sent all them all. The email queue can process automatically using cron jobs. Since PhPList is open source and LimeSurvey is open source, maybe PHPList would share some lessons learned and allow sharing of some of theri current code?

Written by Trixor the 15 Nov 10 at 23:49.

Use the same logic used in Welcome Screen to process the End Message Screen to parse replacement fields correctly.

Use the same logic used in Welcome Screen to process the End Message Screen to parse replacement fields correctly.

Written by eckes the 14 Nov 09 at 21:19.

In order to avoid that a malicious limesurvey installation can give the same vote-code to multiple users it makes sense to generate the vote-code with voter specific data and a random secret.

I am aware that not all users can verify it, but there is still a good changce to spot problems for interested voters.


This would look like this:

Your vote will be documented in the public list like this:

VoteId | Votes
8edb010327bffc70dc2c | 0001: yes 0002: no

The VoteId above is generated personally for you. You can verify this, because we used the following method to generate it:

cut20(sha256("berndeckenfels 1446hhhfdgdfg545"))

(I.e. using your token, appending a random string, calculating the SHA-256 checksum and using the first 20 characters of the hex representation.

In order to avoid that a malicious limesurvey installation can give the same vote-code to multiple users it makes sense to generate the vote-code with voter specific data and a random secret. I am aware that not all users can verify it, but there is still a good changce to spot problems for interested voters. This would look like this: Your vote will be documented in the public list like this: VoteId | Votes 8edb010327bffc70dc2c | 0001: yes 0002: no The VoteId above is generated personally for you. You can verify this, because we used the following method to generate it: cut20(sha256("berndeckenfels 1446hhhfdgdfg545")) (I.e. using your token, appending a random string, calculating the SHA-256 checksum and using the first 20 characters of the hex representation. On Unix you can do: echo "berndeckenfels 1446hhhfdgdfg545" | sha256 | cut -b1-20 Now: voter can check if the published sheet contains vote voter is shure LimeSurvey cant assign the code to two votes voter is shure that the code which is published is not related to the token and nobody (besides limesurvey who generated the random number and stored the code in database) can associate it with the user. (In my example the token is user name, but of course it would be a random string in most cases).

Written by erick the 6 Jul 10 at 21:18.

The function validate_email() in common.php has a big regexp to check valid emails. We already changed it successfully by adding optional semicolon and whitespace at the end of an email.

The function validate_email() in common.php has a big regexp to check valid emails. We already changed it successfully by adding optional semicolon and whitespace at the end of an email.

Written by fjf123 the 8 Sep 11 at 14:55.

it is very good for add one more Attribute, and it must be filled.

it is very good for add one more Attribute, and it must be filled.