View Issue Details

Jump to NotesJump to History
This bug affects 1 person(s).
 8
IDProjectCategoryView StatusDate SubmittedLast Update
15613Bug reportsOtherpublic2019-11-22 16:042020-02-28 16:31
Reporterictfinance Assigned Toollehar  
PrioritynoneSeveritycrash 
Status closedResolutionno change required 
Product Version3.22.7 
Summary15613: Date stamp setting set to "No" after upgrade
Description

Hi,
We upgraded our instance of Limesurvey from version 1.92 to version 3.18. Migration went well.
But we face a very annoying problem: in the active surveys the answers were datestamped when running on version 1.92. But after the upgrade process they are not datestamped anymore. We can see in the survey settings (Notifications & Data -> Responses will not be date stamped. Cannot be changed) that they are indeed not datestamped, and this value cannot be changed. The only way to change this setting is to inactivate the survey, then changing the setting, and re-activate it again. But if we inactivate the surveys then the answers are archived. Fortunately I can import the answers from the archive.
I followed this process, and re-imported answers after having re-activated the survey, but the datestamp info has gone. So I guess that datestamp info was not archived because the survey was set to not save this data. Am I right?
If I export the answers before inactivating the survey and re-import them after re-activation, the problem is the same: datestamp info has gone.
So how can I change the datestamp setting of the surveys without losing datestamp info?

Best regards,

TagsNo tags attached.
Attached Files
limesurvey_survey_51834.lss (534,616 bytes)
Bug heat8
Complete LimeSurvey version number (& build)Version 3.18.0+190923
I will donate to the project if issue is resolvedYes
Browser
Database type & versionMySQL 5.7.27-0
Server OS (if known)ubuntu0.18.04.1
Webserver software & version (if known)
PHP Version7.2

Users monitoring this issue

There are no users monitoring this issue.

Activities

ictfinance

ictfinance

2019-11-22 16:06

reporter   ~54768

This problem has been addressed through support interface to Dorin Iulian Chirițoiu. He requested that I open a bug and mention his name in the report: @cdorin
DenisChenu

DenisChenu

2019-11-23 10:26

developer   ~54769

@ictfinance : can you check if datestamped columns exist in the database ?
ictfinance

ictfinance

2019-11-26 09:20

reporter   ~54780

In the survey_xxxxx tables there is a submitdate column of type datetime
ictfinance

ictfinance

2019-12-06 08:07

reporter   ~54961

Any news about this problem?
Best regards,
Pierre
c_schmitz

c_schmitz

2019-12-19 13:39

administrator   ~55080

Hello Pierre,

does the survey use anonymization/anonymized responses?
cdorin

cdorin

2020-02-22 20:52

reporter   ~56154

Feedback needed
ictfinance

ictfinance

2020-02-28 15:52

reporter   ~56258

Problem is solved. I received instructions about how to add the columns to the database tables, and everything was then OK.
Best regards,

Pierre
ictfinance

ictfinance

2020-02-28 15:56

reporter   ~56259

DenisChenu answered via the forum: https://www.limesurvey.org/forum/installation-a-update-issues/119908-is-it-possible-to-change-the-setting-date-stamp-once-a-survey-is-active#192364

Issue History

Date Modified Username Field Change
2019-11-22 16:04 ictfinance New Issue
2019-11-22 16:04 ictfinance File Added: limesurvey_survey_51834.lss
2019-11-22 16:06 ictfinance Note Added: 54768
2019-11-23 10:26 DenisChenu Note Added: 54769
2019-11-26 09:20 ictfinance Note Added: 54780
2019-11-26 17:38 cdorin Assigned To => cdorin
2019-11-26 17:38 cdorin Status new => assigned
2019-12-06 08:07 ictfinance Note Added: 54961
2019-12-19 13:39 c_schmitz Note Added: 55080
2020-02-22 20:52 cdorin Status assigned => feedback
2020-02-22 20:52 cdorin Note Added: 56154
2020-02-22 20:52 cdorin Assigned To cdorin =>
2020-02-28 15:52 ictfinance Note Added: 56258
2020-02-28 15:52 ictfinance Status feedback => new
2020-02-28 15:56 ictfinance Note Added: 56259
2020-02-28 16:31 ollehar Product Version => 3.22.7
2020-02-28 16:31 ollehar Assigned To => ollehar
2020-02-28 16:31 ollehar Status new => closed
2020-02-28 16:31 ollehar Resolution open => no change required