View Issue Details

IDProjectCategoryView StatusLast Update
15708Bug reports[All Projects] Otherpublic2020-01-14 14:43
Reporterpedesjensen Assigned Tocdorin  
Status assignedResolutionopen 
Product Version3.21.3 
Target VersionFixed in Version 
Summary15708: Data integrity check renames variables in survey_* tables

In our 3.21.4 installation (and also in our previous 3.19.2 installation) the "Check Data Integrity" is malfunctioning. It simply renames columns/variables in the survey_* tables in the database, which makes the affected surveys flawed and useless. We have ~200 active surveys, and the automatic renaming takes place in 14 surveys. It is not all variables/columns in the affected survey tables that get renamed, but in some of them it is only a few and in others it is most of them. There is no obvious pattern in which variables and which surveys are affected.
As seen in the third attached image, apparently the function automatically does some changes, even though the user has not accepted it (besides having initiated the function). This is not good!

I have attached two snapshots (via phpmyadmin) displaying the columns of one particular survey table in the database, before and after the function has been run. Clearly, many of the variables get renamed!

TagsNo tags attached.
Complete LimeSurvey version number (& build)Version 3.21.4+200108
I will donate to the project if issue is resolvedNo
BrowserFirefox 72.0.1 (64-bit)
Database & DB-VersionMarieDB 10.2.25
Server OS (if known)
Webserver software & version (if known)
PHP Version7.2.5




2020-01-14 13:51


Before.JPG (383,374 bytes)
After.JPG (388,620 bytes)
Result_of_Check.JPG (242,318 bytes)

Issue History

Date Modified Username Field Change
2020-01-14 13:51 pedesjensen New Issue
2020-01-14 13:51 pedesjensen File Added: Before.JPG
2020-01-14 13:51 pedesjensen File Added: After.JPG
2020-01-14 13:51 pedesjensen File Added: Result_of_Check.JPG
2020-01-14 14:43 ollehar Assigned To => cdorin
2020-01-14 14:43 ollehar Status new => assigned
2020-01-14 14:43 ollehar Priority none => urgent