View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
20230 | Bug reports | Survey participants (Tokens) | public | 2025-08-20 18:20 | 2025-08-27 10:47 |
Reporter | DenisChenu | Assigned To | |||
Priority | none | Severity | block | ||
Status | new | Resolution | open | ||
Product Version | 6.6.x | ||||
Summary | 20230: Unable to set "Closed access mode" after activation | ||||
Description | When a survey is already activated without token table and token table was create aftre : no way to set as closed access mode. Surye can be answered without tokebn. | ||||
Steps To Reproduce | Steps to reproduceCreate a survey Expected resultToken asled (like X or etc …) Actual resulNo way to update closed/open access mode after activation | ||||
Tags | No tags attached. | ||||
Bug heat | 4 | ||||
Complete LimeSurvey version number (& build) | 6.15. | ||||
I will donate to the project if issue is resolved | No | ||||
Browser | not relevant | ||||
Database type & version | not relevant | ||||
Server OS (if known) | not relevant | ||||
Webserver software & version (if known) | not relevant | ||||
PHP Version | not relevant | ||||
PS : it happen with a copied survey : seems this settings is set 'Open' by default. Just have a urgent call by a prospect about this issue. |
|
By default.. INSERT a record ommitting access_mode will result in access_mode = 'O' |
|
A closer look... access_mode seems obsolete. It is not used in the code anymore. |
|
We had all sorts of issues with tokens in the most recent versions |
|
I just test on https://shnoulle.limesurvey.net If you leave Open access mode when activate : Even with token table : you can enter survey |
|
|
|
I noticed just now... in lime_survey table 'access_mode' ('O' default or 'C') is introduced in 6.15.7. For us one thing is very clear... Token management is faulty in 6.15.7 and 1 or 2 versions before that. |
|
token management: |
|
correction 6.15.4 is also at fault... |
|
As of 5.16.4 this form is not shown anymore (restore old tokens) |
|
correction... |
|
For what it is worth: |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2025-08-20 18:20 | DenisChenu | New Issue | |
2025-08-20 18:22 | DenisChenu | Note Added: 83266 | |
2025-08-20 18:22 | DenisChenu | Bug heat | 0 => 2 |
2025-08-23 10:38 | asshank | Note Added: 83282 | |
2025-08-23 10:38 | asshank | Bug heat | 2 => 4 |
2025-08-24 13:27 | asshank | Note Added: 83283 | |
2025-08-24 14:25 | asshank | Note Added: 83284 | |
2025-08-25 08:53 | DenisChenu | Note Added: 83286 | |
2025-08-25 08:54 | DenisChenu | Note Added: 83287 | |
2025-08-25 08:54 | DenisChenu | File Added: Capture d’écran du 2025-08-25 08-45-21.png | |
2025-08-25 10:00 | asshank | Note Added: 83289 | |
2025-08-25 10:48 | asshank | Note Added: 83292 | |
2025-08-25 11:22 | asshank | Note Added: 83295 | |
2025-08-25 11:44 | asshank | Note Added: 83299 | |
2025-08-25 11:44 | asshank | File Added: Schermafbeelding 2025-08-25 112534.png | |
2025-08-25 11:45 | asshank | Note Added: 83300 | |
2025-08-25 11:46 | asshank | Note Added: 83301 | |
2025-08-25 11:49 | DenisChenu | Relationship added | related to 20193 |
2025-08-25 11:58 | asshank | Note Added: 83305 | |
2025-08-27 10:47 | DenisChenu | Relationship added | related to 20247 |