Hi,

Hope I have posted in the correct section.
Version 1.90+ Build 9642

I have a survey set up that uses tokens and an additional attribute field.
Quite a few of the questions use conditions where 'Token fields' and 'Constant' is used to display the question dependant on the user.
I have a survey instance that is used to build the questionnaire and a live instance where all the build is carried out but when I export from build and import into a live survey instance the conditional logic does not work.

I have found some similar entries that states the same/similar issue is resolved in an earlier version but I am getting the problem with Version 1.90+ Build 9642.

Hope someone can help.

bugs.limesurvey.org/view.php?id=3798&history=1
bugs.limesurvey.org/view.php?id=3940

Do you use the latest 1.90 version for both?

What happens with the conditions? Are they not ported at all or are they not working, correctly?

Hi Mazi,

Exoprting and importing into the same installation/instance (Version 1.90+ Build 9642).
It seems that the conditions table does not get populated with the attibute based conditions.

I created a nasty SQL script that copied the attribute conditions from the original survey into the one I imported and then the attribute conditions worked in the survey.

To my knowledge importing question based conditions works fine at the latest 1.90 version.
Can you test if you have problems with both, question based AND token based conditions or if only the token based conditions fail?!

I created a new survey using LS 1.9. Conditions work fine except when trying to use a value from a token attibute field, such as

Only show Q14 if
attribute_1 >= 2

The conditions in this case are not working and the questions are always shown.

I compared the source code for the page between LS 1.85 where this condition set-up works and LS 1.9 where it does not. At the beginning of the javascript section for conditional questions the section is missing from 1.9 Not sure if that matters but thought I would mention it.

function radio_unselect(radioObj)
{
var radioLength = radioObj.length;
for(var i = 0; i < radioLength; i++)
{
radioObj.checked = false;
}
}

Can you test a different comparison opertor like "= '2'?

I think token attributes are stored as text so comparing a text value and a number may lead to unexpected results.
If so, a regular expression might do the trick.