View Issue Details

IDProjectCategoryView StatusLast Update
15621Bug reportsSurvey participants (Tokens)public2021-03-18 15:51
Reportermos3465 Assigned To 
PrioritynoneSeveritypartial_block 
Status feedbackResolutionopen 
Product Version3.21.2 
Summary15621: Re-accessing a submitted token-based survey will sometimes clear entries from random question groups
DescriptionReferring to this thread in LS forum:
https://www.limesurvey.org/de/foren/design-issues/113928-reopening-a-completed-survey-erases-existing-responses-is-that-normal

We use an old 3.5.0, but others have the same problem with 3.15.9.

Issue:
- we enabled "token-based response persistence"
- we allowed "multiple responses or update responses with one token"

We get occasional reports from respondents and our quality control team, that random variables are cleared upon re-accessing formely submitted surveys.
In our case it's never the complete survey that is wiped, but from what I have seen so far it seems to be a complete question page in each instance.
Order of magnitude: maybe 4-5 % of re-accessed links.

I can rule out that it's the some kind of user's fault, as there were 2 instances where the questions that got cleared upon re-opening the link
1) were mandatory List (radio) question where the users can't "de-select" once an option is selected
2) is itself always shown (relevance=1) and was on a page with relevance=1 (so no messing with earlier questions that could have made the page / question irrelevant)

Steps To ReproduceI have seen that it definitely happened (see above), but couldn't reproduce this myself, as it seems to happen randomly.
TagsNo tags attached.
Complete LimeSurvey version number (& build)3.5.0 (build 180309), also shown for 3.15.9
I will donate to the project if issue is resolvedNo
Browser
Database & DB-Versionmysqlnd 5.0.12-dev - 20150407
Server OS (if known)Apache/2.4.18 (Ubuntu)
Webserver software & version (if known)
PHP Version7.0.28-0ubuntu0.16.04.1

Activities

ollehar

ollehar

2021-03-10 22:26

administrator   ~63195

Please update to the latest version and check if the bug can still be reproduced. Thank you.
mos3465

mos3465

2021-03-18 15:49

reporter   ~63438

Sure! Do you refer to the latest stable (3.25.18) or would you already recommend some 4.x variety for a live production environment?
c_schmitz

c_schmitz

2021-03-18 15:50

administrator   ~63439

Latest 3.x ist just fine.

Issue History

Date Modified Username Field Change
2019-11-26 14:39 mos3465 New Issue
2019-11-26 15:11 cdorin Assigned To => cdorin
2019-11-26 15:11 cdorin Status new => assigned
2021-02-04 21:23 cdorin Assigned To cdorin =>
2021-02-04 21:23 cdorin Status assigned => acknowledged
2021-03-10 21:16 ollehar Product Version => 3.21.2
2021-03-10 22:26 ollehar Status acknowledged => feedback
2021-03-10 22:26 ollehar Note Added: 63195
2021-03-18 15:49 mos3465 Note Added: 63438
2021-03-18 15:49 mos3465 Status feedback => new
2021-03-18 15:50 c_schmitz Note Added: 63439
2021-03-18 15:51 c_schmitz Status new => feedback