I have now tested ExpressionManager integration into LimeSurvey for the
(1) Development + deployed surveys
(2) Token management
(3) Template management
(4) Data entry screen
(5) Printable summary of responses given - passed this through
templatereplace() so that can see the text as the respondent saw it, not as
the survey-designer built it.
In the process, identified 1 small bug in ExpressionManager, and several
bugs in other files (mostly lack of detection of undefined variables).
The only sections I have yet to test are ones that aren't built into any of
my test surveys:
Please try the latest patch (issue_50268-20110617-v2.patch) against the main
limesurvey branch, plus the big survey I uploaded at
Please stress test this to see if it generates any errors for you. I'm not
seeing any problems, so we may be close to ready to consider incorporating
this into the main branch, and into the thinking for the _ci branch.
Get latest updates about Open Source Projects, Conferences and News.