Hi Julien

It's not a major problem and I'm not sure if you may already be aware of it but if a Lime Survey (whether active or inactive) does not have tokens initialised to it (token management) the Drupal site (when you add a 'survey' content) will throw up an error. See attached screenshot.

Just thought you should know and also if anyone else has an issue with this it is documented.

TO EVERYONE: If you do have this problem just ensure you go to 'token management' in Lime Survey and initialise tokens (if if the survey is inactive). This will prevent the error.

Thank you

Stephen

Comments

thedut’s picture

Assigned: Unassigned » thedut

Thanks for this feedback. I'm aware of this issue.
From my point of view, it is due to a bug from the LimeSurvey software : Surveys with the "token-based response persistence" option enabled *should* have a token table.
Anyway, it causes a fatal error on my module... I plan to dig on and fix this issue on the new release.

Ya777’s picture

Hi Stephen,

What I can do with this issue if the Survey "active"?

Thank you,

thedut’s picture

In order to solve this issue, you have to use tokens invitiation from your LimeSurvey admin interface. This feature is called :
- 'switch to closed-access mode',
- or 'initialize token'
- or 'create tokens table'
You can create the tokens table if your survey is either active or inactive, it does not matter.

dobrzyns’s picture

I also am experiencing this and DO NOT want to use tokens. That's a poor solution to require tokens.

thedut’s picture

Hello dobrzyns,

I inform you than I'm able to use the LimeSurvey Sync module without token.
I guess something fails into your LimesSurvey admin interface configuration : You probably enable the token-based response persistence and you should not if you don't want to use token.
As a solution : Disable the token-based response persistence and it will work without a token table. At least it works for me.
if it does not work, share the screenshot of your survey node page.

thedut’s picture

This is duplicate issue of : fatal error when trying to add content->Survey : but I still can't reproduce it !

thedut’s picture

Status: Active » Postponed (maintainer needs more info)

More documentation on this issue :
A fatal error occurs on adding a new survey content.
In order to solves it : Create a token table on the LimeSurvey admin interface.

This is a real issue : 6 users have reported it on the LimeSurvey_Sync module :

The point is : I can't reproduce it, I need more informations in order to definitvely fix it.
I have tested to create a new survey contents with many conditions but I fail in reproducing this issue. For the detail : creatin a survey node with or without a token table, with the tokenpersistance parameter set to Yes and No. And exploring the LimeSurvey Sync php code.

In order to help me to solve this issue please : provide your survey : on your LimeSurvey admin interface, got to 'Export survey' and provide the LimeSurvey XML survey file (*.lss).

spessex’s picture

Hi

Sorry I didn't see this. I've just experienced the problem and it looks like that if 'any' single one of your Lime Surveys does not have tokens enabled it will lead to the exception problem. So for example if you 20 surveys and 1 of them does not have a token table it will throw the exception.

thedut’s picture

StatusFileSize
new6.04 KB

Thank you spessex,

Unfortunatelly I still can' reproduce this issue : I have tested to add a survey on a LimeSurvey install with many surveys, some with a token table and some without a token table.

This issue has been reported again, on LimeSurvey Sync module v7.x-1.4 by farzantabrizi : I still can't reproduce it but I provide a fix that may succeed.
To farzantabrizi : please don't create a token table et replace the ls_api/limesurvey_sync_api_survey.inc file by the attached one and report.

thedut’s picture

I have include the fix from #9 into the LimeSurvey Sync module 7.x.1.5 and the 6.x-1.5 versions.
I hope it will improve this issue.
Please report if you see any change.
At least the error message should be different.

thedut’s picture

Version: 7.x-1.2 » 7.x-1.4
Status: Postponed (maintainer needs more info) » Closed (fixed)

Hello,

Working on a dev version, I have succeeded in reproducing this issue. The fix from #9 did fix it !
I close this thread as Fixed into the 7.x-1.5 release.