Has there been any status update for this issue? It's still effecting me...
Thanks!

I think it's work in progress, some details are discussed here: http://bugs.limesurvey.org/view.php?id=4608

This is not a duplicate of 4608, but anothe bug.
I'm looking at this

This bug is not an importsurvey bug, but an exportsurvey bug.
The cfieldname in the exported survey is

• <cfieldname><![CDATA[25795X465X5168nder]]></cfieldname>
  Instead of
• <cfieldname><![CDATA[25795X465X5168ander]]></cfieldname>

Mazi, can you test again from a new survey with teh very latest SVN code, as Cartsen has fixed issue in the file I think.
If you can copy this bug on latest codebase, please let me know.

Thibault

PS: a test survey in english is easier for me to test ;-)

I updated to the latest SVN version, imported the survey again and the conditions were copied. BUT: They do not work. Take a look at the attached condition screen screen shot and the DB table screen shot:
The field code for the "andere" field is "ander" while the first character "a" seems to be missing at the DB. it should read
72986X746X13029ander instead of
72986X746X13029nder

I think that's the reason why the condition doesn't work. No matter what you answer at the "andere" field, the following question is never shown.

Hope this helps...

Hi Mazi,

The pb is in the ".lss" file so importing again this buggy file will result in a buggy survey in any case (even if LS was fixed in the meantime).

What I'd like you to do is to build another fresh new survey with teh same kind of questions and conditions. Then export it and import-it again.
Since this is a brand new survey, can you do this one in English ?

TIA,
Thibault

I created a new test survey, exported it and imported it again. At the imported version the reference to the previous answer doesn't work correctly, I get:
Why did you rate "Other" = Error(21839X747X13122other) -> all IDs are wrong.

The condition seems to be copied correctly though, if I answer "no answer" at Q1, item "other", the second question is skipped as expected.

Mazi, if I understand your last post correctly, this means that the export bug is already fied in latest SVN, but the INSERTANS bug remains.
Am I right ?

If yes, the this means this ticket can be closed and work must be done on bug 4608 instead.

Thibault, thanks for summarizing my findings ;-)

Not only have I summarized your meaning, but at the same time I've been able to reproduce the bug.

In fact it does occur at import time and may have been here since the new LSS format was introduced.

Fixed in rev 9203.
Thx Mazi for the report and the tests.
Thibault

Released in latest Plus version