View Issue Details

This bug affects 1 person(s).
 4
IDProjectCategoryView StatusLast Update
06941Bug reportsInstallationpublic2012-11-23 15:09
Reporterjussibus Assigned Toc_schmitz  
PrioritynormalSeverityminor 
Status closedResolutionunable to reproduce 
Product Version2.00+ 
Summary06941: Survey equations got wrong after upgrade 1.92 -> 2.00
Description

A survey with equations like some_code.NAOK=="something" were messed up when LimeSurvey got upgraded from version 1.92 to 2.00+.

Originally the equations were like some_code.NAOK=="something".

Then after the upgrade the equations were like 48452X10X181.NAOK=="something" but still working as the id's pointed to correct questions

When the survey was copied in 2.00, the equations didn't work anymore as the id's didn't point to any question within the new survey.

Steps To Reproduce

I can't reproduce this anymore. Tried with 1.92 with similar survey I had. Upgraded LimeSurvey to version 2.00+ Build 121117 but the equations were correct.

It wasn't me who did the original LimeSurvey upgrade that caused the problem so I can't be sure what really happened. Perhaps something went wrong with the upgrade and the database didn't get upgraded correctly.

Also, I was testing against Version 2.00+ Build 121117. Previously, when the problem occurred, the version 2.00+ build number was smaller.

Additional Information

Not sure if this report is of any use as can't reproduce it. Also, I don't have enough information.

One of the original relevance equations was:
!(pankin_sijainti.NAOK == "10" or pankin_sijainti.NAOK == "101" or pankin_sijainti.NAOK == "102" or pankin_sijainti.NAOK == "103" or pankin_sijainti.NAOK == "110" or pankin_sijainti.NAOK == "117" or pankin_sijainti.NAOK == "126" or pankin_sijainti.NAOK == "131" or pankin_sijainti.NAOK == "140" or pankin_sijainti.NAOK == "141" or pankin_sijainti.NAOK == "143" or pankin_sijainti.NAOK == "159" or pankin_sijainti.NAOK == "163" or pankin_sijainti.NAOK == "168" or pankin_sijainti.NAOK == "17" or pankin_sijainti.NAOK == "185" or pankin_sijainti.NAOK == "26" or pankin_sijainti.NAOK == "44" or pankin_sijainti.NAOK == "45" or pankin_sijainti.NAOK == "46" or pankin_sijainti.NAOK == "56" or pankin_sijainti.NAOK == "59" or pankin_sijainti.NAOK == "60" or pankin_sijainti.NAOK == "64" or pankin_sijainti.NAOK == "66" or pankin_sijainti.NAOK == "74" or pankin_sijainti.NAOK == "75" or pankin_sijainti.NAOK == "80" or pankin_sijainti.NAOK == "82" or pankin_sijainti.NAOK == "96")

After the upgrade it was changed to:
!(48452X10X181.NAOK == "10" or 48452X10X181.NAOK == "101" or 48452X10X181.NAOK == "102" or 48452X10X181.NAOK == "103" or 48452X10X181.NAOK == "110" or 48452X10X181.NAOK == "117" or 48452X10X181.NAOK == "126" or 48452X10X181.NAOK == "131" or 48452X10X181.NAOK == "140" or 48452X10X181.NAOK == "141" or 48452X10X181.NAOK == "143" or 48452X10X181.NAOK == "159" or 48452X10X181.NAOK == "163" or 48452X10X181.NAOK == "168" or 48452X10X181.NAOK == "17" or 48452X10X181.NAOK == "185" or 48452X10X181.NAOK == "26" or 48452X10X181.NAOK == "44" or 48452X10X181.NAOK == "45" or 48452X10X181.NAOK == "46" or 48452X10X181.NAOK == "56" or 48452X10X181.NAOK == "59" or 48452X10X181.NAOK == "60" or 48452X10X181.NAOK == "64" or 48452X10X181.NAOK == "66" or 48452X10X181.NAOK == "74" or 48452X10X181.NAOK == "75" or 48452X10X181.NAOK == "80" or 48452X10X181.NAOK == "82" or 48452X10X181.NAOK == "96")

TagsNo tags attached.
Bug heat4
Complete LimeSurvey version number (& build)121117
I will donate to the project if issue is resolvedNo
BrowserSafari
Database type & version?
Server OS (if known)Linux
Webserver software & version (if known)Apache
PHP Version?

Users monitoring this issue

There are no users monitoring this issue.

Activities

jussibus

jussibus

2012-11-23 10:19

reporter   ~22439

The original discussion is here:
http://www.limesurvey.org/en/forum/can-i-do-this-with-limesurvey/88770-importing-or-copying-surveys-break-relevance-equations

c_schmitz

c_schmitz

2012-11-23 15:09

administrator   ~22444

If the issue is not reproducible anymore it is most likely already fixed.
We can only fix issues that are reproducible. If you should be able to reproduce the issue using the latest build please re-open the issue.

Thank you.

Issue History

Date Modified Username Field Change
2012-11-23 10:17 jussibus New Issue
2012-11-23 10:19 jussibus Note Added: 22439
2012-11-23 15:09 c_schmitz Note Added: 22444
2012-11-23 15:09 c_schmitz Status new => closed
2012-11-23 15:09 c_schmitz Assigned To => c_schmitz
2012-11-23 15:09 c_schmitz Resolution open => unable to reproduce