View Issue Details

This bug affects 1 person(s).
 4
IDProjectCategoryView StatusLast Update
14610Bug reportsSurvey takingpublic2021-02-07 12:32
Reporterachstil Assigned Tocdorin  
PrioritynoneSeveritypartial_block 
Status closedResolutionopen 
Product Version3.15.x 
Summary14610: ResumeLater, when multiple responses allowed, messes up SCID
Description

When multiple responses are allowed, it seems SCID in save parameter gets confuesed. That is - limesurvey cant keep track of which of the multiple responses I have saved, and which I am resuming.

Steps To Reproduce

The survey is only accessible via tokens.
The survey allows multiple responses.
One hidden questions (Lets called it: "QH") is prefilled via URL. Options are O1, O2, O3.

User begins survey (via link from another webpage). This survey has QH = O1. User Saves it. Receives email (email1). Link in email has SCID = 123
USer closes window.
User begins survey (via link from another webpage). This survey has QH = O2. User saves it. Receives email (email2). Link in email has SCID = 124
User closes window.
User clicks on link in email1. User is correctly taken to survey with QH = O1. URL shows SCID = 123
User saves and closes window.
User clicks on link in email2. User is correctly taken to survey with QH = O2. URL shows SCID = 124
USer saves and closes window.
User clicks on link in email1. User is WRONGLY taken to survey with QH = O2. Inspecting the URL show, that the SCID is now 124.

Additional Information

Don't know if this is relevant: https://manual.limesurvey.org/SaveResume

TagsNo tags attached.
Bug heat4
Complete LimeSurvey version number (& build)Version 3.15.5+181115
I will donate to the project if issue is resolvedYes
BrowserFirefox, chrome, Edge
Database type & versionPostgres11
Server OS (if known)Ubuntu 18.04
Webserver software & version (if known)Apache
PHP Version7.2.11

Users monitoring this issue

There are no users monitoring this issue.

Activities

cdorin

cdorin

2019-12-03 15:26

reporter   ~54922

Do you have any .lss file where you can easily replicate the issue ? If yes, could you please attach it to this ticket? (please make sure to check everything in 3.20.x)

cdorin

cdorin

2021-02-07 12:32

reporter   ~61974

No feedback provided - ticket closed

Issue History

Date Modified Username Field Change
2019-03-06 15:31 achstil New Issue
2019-12-03 15:26 cdorin Note Added: 54922
2019-12-03 15:26 cdorin Assigned To => cdorin
2019-12-03 15:26 cdorin Status new => feedback
2021-02-07 12:32 cdorin Status feedback => closed
2021-02-07 12:32 cdorin Note Added: 61974