View Issue Details

Jump to NotesJump to History
This bug affects 1 person(s).
 2
IDProjectCategoryView StatusDate SubmittedLast Update
03534Bug reportsData Entry (non public)public2009-08-04 12:272009-08-12 14:14
ReporterGiovanni Assigned Toc_schmitz  
PrioritynormalSeverityminor 
Status closedResolutionno change required 
Product Version1.85+ 
Summary03534: Duplicated rows with same token on browsing responses
Description

Dear all,

I've some problems on a live survey that I'm doing.
When I go to check responses browsing them I found some duplicated tokens with strange data recorded.
One time I founded two lines with the same token that was either completed N and the other line with completed Y.
Today I've founded another dangerous situation with 3 lines that have the same token with one of these empty, one with few data and the other one with all answers. I'm a little bit afraid that something could damage my database. Please, gently have a check if these situations are dangerous or not and why this can happen.
Thanks Giovanni

TagsNo tags attached.
Attached Files
101a601.jpg (17,741 bytes)   
101a601.jpg (17,741 bytes)   
Bug heat2
Complete LimeSurvey version number (& build)
I will donate to the project if issue is resolved
Browser
Database type & version
Server OS (if known)
Webserver software & version (if known)
PHP Version

Users monitoring this issue

There are no users monitoring this issue.

Activities

c_schmitz

c_schmitz

2009-08-12 14:14

administrator   ~09110

I looked at the data and your bug report. I honestly don't think this is a problem of LimeSurvey but more of a problem with the particular user browser/connction.
Especially old infrastructure (like IE6 with a proxy in between) tends to have these problems.
In addition in this particular case the user must have had some error on screen (I would bet it was some kind of proxy or session expired error) - that's why the user tried again to fill the survey.

I would strongly recommend to activate 'Token-based answer persistence' in your survey settings to keep duplicate submission to a minimum.
That way a user, who is crashing out due to some error, can restart the survey without having lost all his answers and using the same result set.

Issue History

Date Modified Username Field Change
2009-08-04 12:27 Giovanni New Issue
2009-08-04 12:27 Giovanni Status new => assigned
2009-08-04 12:27 Giovanni Assigned To => user372
2009-08-04 12:27 Giovanni File Added: 101a601.jpg
2009-08-12 14:03 c_schmitz Assigned To user372 => c_schmitz
2009-08-12 14:14 c_schmitz Note Added: 09110
2009-08-12 14:14 c_schmitz Status assigned => closed
2009-08-12 14:14 c_schmitz Resolution open => no change required