Interesting, I was looking for something like this last Summer, but I guess this plugin wasn't around then.

People are always asking for "integrating" products but that means a LOT of different things to different people. It's convenient to have the WP users table and LS users table but doesn't solve the problem of having "private," password-controlled surveys. You have to use tokens to control access in LS. The Central Participants Database will help to pull together a unified view of tokens by participant for the administrator to use, but it still lacks password protection and doesn't have an interface for the Participants themselves to use. But having the CPD data structure at least gives you a place to hook into.

I think people are looking for a "research panel" application. Commercial equivalents are Vovici, Globalpark, etc. I like the idea of working with Buddypress or Drupal and starting with the concept that "survey takers" are users, but different kinds of users than "survey builders." Each needs their own distinct interface.

Fred wrote: The Central Participants Database will help to pull together a unified view of tokens by participant for the administrator to use, but it still lacks password protection and doesn't have an interface for the Participants themselves to use. But having the CPD data structure at least gives you a place to hook into.

Such a username/password feature is on our wish list as well. Problem is that we do all the coding, bug fixing and support at our free time which is pretty limited due to "real" jobs, friends and family. Sometimes users/companies sponsor new features which makes it easier because when being paid you can buy your wife a new pair of shoes as compensation for telling her "sorry, I have to finish this coding stuff, we can't watch TV this evening"

Fred wrote: I think people are looking for a "research panel" application.

That's the idea behind the CPDB project. It is just a first version with basic features but once we notice that users love it, we will extend its features.

You can add such things as a feature request at our feature tracker . Please describe your idea as detailed as possible and try to outline a suitable solution/implementation as well.

The LimeSurvey team is doing an awesome job. We should all make Valentine's Day donation

Fred wrote: Interesting, I was looking for something like this last Summer, but I guess this plugin wasn't around then.

People are always asking for "integrating" products but that means a LOT of different things to different people. It's convenient to have the WP users table and LS users table but doesn't solve the problem of having "private," password-controlled surveys. You have to use tokens to control access in LS.

Exactly, every admin want tokens to be tailor made i.e. he might follow some arbitrary algorithm while making tokens. Tokens for different users should be different and shouldn't be guessable! And that's where the main problem lies. Syncing tokens table and WP tables is not a problem. You can't make username/email-address as a token,coz than any user can take another user's survey(given token is known to him!) which leaves the option of random tokens and for that another plugin specific table will be required in WP. I wanted this plugin to be as light as possible but of course with some proper purpose! I might work on introducing token-syncing feature soon!

Added the "Tokens syncing" feature!
Now it should be fairly easy to do what you're looking for! Make your surveys private and enable tokens. Fill in the customization options in plugin screen. If you only want users with role 'editors' to take a survey with sid=xyz, check 'editors' and give xyz as sid and all users with role 'editor' will be given a unique and random token. When they login in WP, they should be able to give the survey only if they have the token!

I wanted to test it, so yesterday I installed Wordpress/Buddypress/Surveypress, but didn't have the time to make the necessary configuration of surveypress. Today I wanted to log into wordpress and an errormessage of survey press is blocking the whole installation. When I want to do the login I get the following message:

"unable to update records in ls table with given credentials!".

I can't get logged in and I can't skip this message either.

Remove the plugin and try again?

Yup, that's what I've done. Just wanted to let you know. After I have put an underscore in front of the plugin folder I could log in normally.

holch wrote: Yup, that's what I've done. Just wanted to let you know. After I have put an underscore in front of the plugin folder I could log in normally.

underscore as in '_surveypress' folder name? Does it works after that? Make sure debug mode is set to off!

After renaming the folder name to '_surveypress' I can login normally, but of course, the plugin doesn't work. However, once I was logged in, I switched the folder back to 'surveypress' and after a reload of the page the plugin was available again to make configurations. Now I have to install a copy of Limesurvey to make sure it is running.

But I guess the error message shouldn't block the login to Wordpress. It took me quite a while until I figured out that it was not my PW that was wrong, but that the problem had to do with Limesurvey/Surveypress.

holch wrote: After renaming the folder name to '_surveypress' I can login normally, but of course, the plugin doesn't work. However, once I was logged in, I switched the folder back to 'surveypress' and after a reload of the page the plugin was available again to make configurations. Now I have to install a copy of Limesurvey to make sure it is running.

But I guess the error message shouldn't block the login to Wordpress. It took me quite a while until I figured out that it was not my PW that was wrong, but that the problem had to do with Limesurvey/Surveypress.

Corrected it! But it's explicitly mentioned,
"Do not set 'debug_mode' to true until database connection error message is gone!" though in your case plugin should have degraded peacefully! Added the fix. Thanks!

Hmm, I have not set debug_mode to true at all. So this can't be the problem. I did a clean an simple install of Wordpress, then Buddypress and Surveypress via de installation function within Wordpress. I didn't switch the debug mode on.