@ lithium: If I remember correctly it's not possible to set conditions based on tokens after import correctly ==> have a look at the notes of Lemeur in 03798

@ Lemeur: Am I right about import of a survey with conditions based on tokens?

@ Lemeur: If I imported the attached survey on my installation (latest revision from SVN), activate the survey and DON'T set to use tokens and run the survey ==> I get the following error:
Fatal error: Call to a member function RecordCount() on a non-object in /home/.sites/962/site989/web/limesurvey/common.php on line 6908

This ticket is certainly that it is a duplicate of 03798.

Sorry Matador I don't understand your sentence "If I remember correctly it's not possible to set conditions based on tokens after import correctly".

The bug in 3798 prevented a correct import of surveys with conditions based on tokens. Once the survey has been incorrectly imported (conditions have been tampered with by the import system), it is not possible to fix it with the LimeSurvey GUI => you have to delete the survey, upgrade the LS installation, and then import again the survey from a correct survey structure (one that haven't been imported yet).

However, it is possible to set new conditions on tokens on a survey that has just been imported.

Hope this helps,
Thibault

@ lemeur: I meant, that conditions based on tokens are invalid and are not working directly after importing a survey structure.

@ lemeur: Can you reproduce the error message "Fatal error: Call to a member function RecordCount() on a non-object in..." and fix it?

"Once the survey has been incorrectly imported (conditions have been tampered with by the import system), it is not possible to fix it with the LimeSurvey GUI"

I'm not sure what you mean by this. Any conditions based on tokens after import just seemed to not exist. To fix it I manually created a token table and recreated the conditions. Do you mean they are hiding in the db or somewhere else invisible to the GUI?

Would it be reasonable to have Limesurvey automatically initialize a token table when you import a survey with conditions based on tokens? Or is a non-existent token table not the root of the problem.

[Quote]Do you mean they are hiding in the db or somewhere else invisible to the GUI?[/Quote]

Yes exactly.

[Quote]is a non-existent token table not the root of the problem.[/Quote]
Non existent token is not the cause of the Import problem.
In LS 1.87 you can safely import surveys having conditions on tokens even if the token table doesn't exist ==> of course if you don't set the token table conditions won't work... hence the RecordCount error reported by Matador (at least it seems to be).

Thibault

The error reported by Matador is fixed in rev 8180.