View Issue Details

IDProjectCategoryView StatusLast Update
14401Bug reports[All Projects] Survey participants (Tokens)public2019-01-07 14:59
ReporterMaziAssigned Toc_schmitz 
PrioritynoneSeverityminor 
Status assignedResolutionopen 
Product Version3.15.x 
Target Version3.16.xFixed in Version 
Summary14401: If options for "token based answer persistance" and "Allow multiple responses..." are enabled, "uses left" is not decreased
Description

If at a closed survey the options for "token based answer persistance" and "Allow multiple responses or update responses with one token:" are enabled, the uses left value doesn't get decreased on submit. I think this was the case at previous versions like 2.6 LTS. It can cause the following problem: If a user now changes those two settings by switching them off, all participants can participate once more - since uses left is 1 on survey start - so we end up with 2 data sets for each participant.

Steps To Reproduce
  1. Use a non-anonymous survey with "token based answer persistance" and "Allow multiple responses..." enabled.
  2. Add a test user.
  3. Add a data set for that user.
  4. Change those two settings by switching them off.
  5. Take the survey with your test user again and submit another response.
  6. You end up with two response data sets for the same user though it is a closed survey with "uses left" being set to 1 as default value.
TagsNo tags attached.
Complete LimeSurvey version number (& build)3.15.5+181115
I will donate to the project if issue is resolvedNo
BrowserChrome
Database & DB-VersionMySQL 5
Server OS (if known)Ubuntu 14 TLS
Webserver software & version (if known)Apache 2
PHP Version7.0

Activities

DenisChenu

DenisChenu

2019-01-07 14:59

developer   ~50123

I think « update responses with one token» (with «token based answer persistance») don't use useleft

https://github.com/LimeSurvey/LimeSurvey/blob/05f0bf840c58bd4f3526527706eb8cfc8a00e7b2/application/controllers/survey/index.php#L511

I think in 2.6lts : use left was decremented in all situation.

Issue History

Date Modified Username Field Change
2019-01-07 10:45 Mazi New Issue
2019-01-07 10:45 Mazi Status new => assigned
2019-01-07 10:45 Mazi Assigned To => c_schmitz
2019-01-07 14:59 DenisChenu Note Added: 50123