Is your survey mode "all in one page"?

Hi,
No, survey format is "group by group".
Cheers

Ok, so in group by group your respondent should jump to the latest group he/she was on when closing the browser, if the survey is not anonymous.

Weird. Not sure how to help right now, because this should work.

holch wrote: …
Weird. Not sure how to help right now, because this should work.

Yes,

Same,

Checked (again) in 3.22.24 / git : OK no issue.

Yes, that's why I would be interested in learning how the system works for bringing the user back where he left. I suppose it doesn't rely on the use of cookies? Because only the PHPSESSID cookie is present.
And in fact it works if the browser is not closed. If I fill in the survey and leave by closing my browser tab, and then reopen a new tab and use the url to the survey, I come back where I left. But if I close my browser and open it and go to the url of the survey, I arrive on the first page, and LS creates a new entry in the table of responses.
Best regards,

Pierre

Coide is here : github.com/LimeSurvey/LimeSurvey/blob/3....urvey/index.php#L506

It reload existing response in $_SESSION

Pierre, can you try with a different browser to eliminate the possibility of a browser add-on/plugin causing the problem?

Thanks for the link. I tracked down the problem: $token is empty.
On line 491 I found this:
else {
// Must never happen : unset invalid token for the second time
$token = null;
}
This code was embedded in the build released on the 25th of May, but has been deleted on the 25th of May by Shnoulle
Now everything works as expected.

Thanks to all of you for your help.

OK, the problem described at the top is indeed solved. But another problem appeared. We have another survey, where there is one single participant, with a token. The token has been given to several people, and they use this token in order to answer the survey. Each time a participant connects to the survey, a new record is created in the table with the responses. Now I made the change described above for fixing the problem, it doesn't work anymore: after entering the token, I get a blank screen.
I just used Comfort update to install the latest update (Version 3.22.24+200630), and the problem persists.
Any idea?
Best regards,
Pierre

ictfinance wrote: Thanks for the link. I tracked down the problem: $token is empty.
On line 491 I found this:
else {
// Must never happen : unset invalid token for the second time
$token = null;
}
This code was embedded in the build released on the 25th of May, but has been deleted on the 25th of May by Shnoulle
Now everything works as expected.

Thanks to all of you for your help.

Arggg ¿ 2 hours bug but a release between …
Sorry for this

I get a blank screen.

Please activate debug mode.

I just used Comfort update to install the latest update (Version 3.22.24+200630), and the problem persists.

No know issue with 3.22.24

Problem solved: php memory_limit was too low.