View Issue Details

Jump to NotesJump to History
This bug affects 1 person(s).
 4
IDProjectCategoryView StatusDate SubmittedLast Update
13202Bug reportsSurvey participants (Tokens)public2018-01-18 11:072021-09-07 08:26
Reporterrbaier Assigned Togalads  
PrioritynoneSeverityminor 
Status closedResolutionfixed 
Product Version3.0.x 
Summary13202: When "Allow public registration" is set, then using "Use CAPTCHA for survey access"
Description

In LS Version 2.72.5+171121 this error can also be observed.
When "Allow public registration" ist set (In a survey using a token table), and also "Use CAPTCHA for survey access" is set, then a participant will always be redirected to the registration page of the suvey, no matter if he uses an URL containing the token.
Only way to stop this behaviour is unset "Use CAPTCHA for survey access".

In LS Version 3.04 things have changed a little. When "Allow public registration" ist set (In a survey using a token table), and also "Use CAPTCHA for survey access" is set, then a participant is directed to a page where he is asked to fill in the answer of the CAPTCHA question. But he cannot do this easily, as the input field is covered partially.

Steps To Reproduce

I have created a survey on the demo server:
https://demo.limesurvey.org/index.php?r=admin/tokens/sa/browse/surveyid/672316

You don't have to register for this survey to see the issue. Instead you can go to the participants table and use the cog-wheel-link oa a participant.

TagsNo tags attached.
Bug heat4
Complete LimeSurvey version number (& build)3.0.4+180116
I will donate to the project if issue is resolvedNo
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

ollehar

ollehar

2021-03-10 21:19

administrator   ~63139

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

galads

2021-09-07 08:26

reporter   ~66353

Hello rbaier,

we have asked for feedback on this issue. Because we did not get an answer we assume that the issue is resolved.
However, should you be able to reproduce the issue using the latest version, please feel free to re-open the issue and give us exact details on how to reproduce it.

Thank you and best regards,

galads

Issue History

Date Modified Username Field Change
2018-01-18 11:07 rbaier New Issue
2018-01-18 12:08 ollehar Assigned To => ollehar
2018-01-18 12:08 ollehar Status new => confirmed
2018-01-18 17:41 ollehar Assigned To ollehar => markusfluer
2021-03-10 21:19 ollehar Assigned To markusfluer =>
2021-03-10 21:19 ollehar Status confirmed => feedback
2021-03-10 21:19 ollehar Note Added: 63139
2021-09-07 08:26 galads Assigned To => galads
2021-09-07 08:26 galads Status feedback => closed
2021-09-07 08:26 galads Resolution open => fixed
2021-09-07 08:26 galads Note Added: 66353
2021-09-07 08:26 galads Bug heat 2 => 4