please have a look at
You can find my answers below...
Am 03.03.2014 20:31, schrieb Rystraum
I don't think that there is any option for
this, but maybe others have some ideas?
First off, here's where I am right now: I'm fairly
familiar with the admin code (as I'm also working on porting
the old limesurvey renderWrappedTemplate with Yii's built in
renderer). I'm familiar with PHP but still learning about
Yii. I've only touched controllers, and yii's rendering so
far. I'm using LimeSurvey Version 2.05+.
Here are my questions.
1) How do you embed a survey in a site while preventing
creation of a response every single time the survey is loaded?
(as opposed to creating the response only after the survey has
Since this information is stored at the DB you
have to touch the core tables to extend this.
2) If I want to customise the admin users information (add
more fields), is there a way to do that without touching the
DB? Or is that the only way?
From my point of view this sounds like an
additional level that has to be added to the general Limesurvey
right module. Since that affects nearly every feature because the
rights details have to be adjusted and to my knowledge there is no
existing mechanism for this, I wouldn't want to touch this.
3) I'd like to implement a sort of department admin and
survey administrators under a department admin. Survey
administrators can only manage their own surveys. Surveys
created by survey administrators are automatically tied to
their department. The department admin can only manage surveys
created under their department. I imagine this will be an
addition of a department model, changes to the survey model
and the admin user model. Is there a mechanism for such right
now? Or do I have to write it myself for now?
That's the way Limesurvey works when not using
tokens. Each new data set is treated as a single response.
4) Is it possible for one user to answer the same survey
but it would be recorded as a different response every time?
Which code paths would I need to modify to make this possible?
This is really repurposing Limesurvey as a generic form
generator for the non-technical.
When using tokens there are options to either let user correct
existing answers when calling the surevy with an already used
token or to create a new data set.
Not sure if this is the proper venue to ask some of these
questions and would appreciate proper guidance on where I
should be asking these things.
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works.
Faster operations. Version large binaries. Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
limesurvey-developers mailing list