View Issue Details

This issue affects 1 person(s).
 10
IDProjectCategoryView StatusLast Update
10476Bug reportsSurvey editingpublic2016-06-06 15:16
Reporterpmonstad Assigned ToLouisGac 
PrioritylowSeverityminor 
Status closedResolutionfixed 
Product Version2.50.x 
Summary10476: correct use of term token?
Description

When Edit survey text elements and settings there are a menu to the right "Token". I wonder if the is correct term to use here? What about Access? My opinion is the term Token is somewhat confusing used here. See screenshot.

TagsNo tags attached.
Attached Files
Bug heat10
Complete LimeSurvey version number (& build)160215
I will donate to the project if issue is resolvedNo
Browserirrelevant
Database type & versionirrelevant
Server OS (if known)irrelevanti
Webserver software & version (if known)irrelevant
PHP Versionirrelevant

Users monitoring this issue

There are no users monitoring this issue.

Activities

DenisChenu

DenisChenu

2016-02-16 12:22

developer   ~35217

This part seems really linked to token only.
If, at a time, we move token to a plugin : this part can be removed from core i think.
Without token : this part aren't really used

holch

holch

2016-02-16 15:49

reporter   ~35230

I actually agree with Pmonstad. I think this should be something like Controlled Access or something. Yes, it is about token, but token is the little code and nothing else. What actually happens is to control access to the survey.

DenisChenu

DenisChenu

2016-02-16 15:52

developer   ~35231

Last edited: 2016-02-16 15:53

Then, maybe : fix the "title" of the token management too ?

c_schmitz

c_schmitz

2016-02-16 16:58

administrator   ~35238

Last edited: 2016-02-16 16:58

The token term has always been profoundly confusing.

But finding a good term is difficult and also the workflow has to be revamped.

I think it is a bad idea that the existence of the token table determines the usage of tokens and there is no separate switch.

Anyway. there is no immediate solution needed, the tab was named like this already in 2.06 so this has a very low priority right now.

pmonstad

pmonstad

2016-02-16 18:35

updater   ~35249

Token Management is OK as is is related to tokens. This menu as mentioned has less to do with tokens. It controls access to the survey and some token settings. I suggest a rename of the menu to Tokens & Access. No need to do other changes, are there? Adding access to the menu name will reflect a couple of settings found here: Anonymized responses, Allow public registration. An alternative would be to move these two settings to the menu Publication & access control. Perhaps an even better solution?

DenisChenu

DenisChenu

2016-02-16 19:01

developer   ~35252

Right access control ~near~ token.

But : expire is totaly different from token access :)

pmonstad

pmonstad

2016-02-16 19:09

updater   ~35253

Hm, after rethinking I keen on my last statement: move Anonymized responses, Allow public registration from the Tokens menu and into the Publication & access control menu. I feel this is quite logical.

What do you say?

c_schmitz

c_schmitz

2016-02-16 22:28

administrator   ~35269

It was there before but the problem that these settings have no effect if the user does not use tokens - so it is even more confusing. So that's why I grouped all token-relevant settings on that 'Tokens' tab starting in 2.0.

Moving it back to the access tab will not enhance the situation now so I will leave it as it is.
With the mentioned needed revamp all access relevant settings should be on one page with explanations and a logic/wizard to configure - but as said: no priority right now.

DenisChenu

DenisChenu

2016-02-17 07:40

developer   ~35279

+1 for c_schmitz ;)

LouisGac

LouisGac

2016-06-03 15:08

developer   ~39198

Now, it's called "Survey participant"

c_schmitz

c_schmitz

2016-06-06 15:16

administrator   ~39252

Version 2.50 Release 160606 released

Issue History

Date Modified Username Field Change
2016-02-16 12:20 pmonstad New Issue
2016-02-16 12:20 pmonstad File Added: Skjermbilde 2016-02-16 kl. 12.18.27.png
2016-02-16 12:22 DenisChenu Note Added: 35217
2016-02-16 15:49 holch Note Added: 35230
2016-02-16 15:52 DenisChenu Note Added: 35231
2016-02-16 15:53 DenisChenu Note Edited: 35231
2016-02-16 16:58 c_schmitz Note Added: 35238
2016-02-16 16:58 c_schmitz Assigned To => c_schmitz
2016-02-16 16:58 c_schmitz Status new => acknowledged
2016-02-16 16:58 c_schmitz Note Edited: 35238
2016-02-16 17:00 c_schmitz Priority normal => low
2016-02-16 18:35 pmonstad Note Added: 35249
2016-02-16 19:01 DenisChenu Note Added: 35252
2016-02-16 19:09 pmonstad Note Added: 35253
2016-02-16 22:28 c_schmitz Note Added: 35269
2016-02-17 07:40 DenisChenu Note Added: 35279
2016-04-21 15:13 c_schmitz Assigned To c_schmitz =>
2016-06-03 15:08 LouisGac Note Added: 39198
2016-06-03 15:08 LouisGac Status acknowledged => resolved
2016-06-03 15:08 LouisGac Resolution open => fixed
2016-06-03 15:08 LouisGac Assigned To => LouisGac
2016-06-06 15:16 c_schmitz Note Added: 39252
2016-06-06 15:16 c_schmitz Status resolved => closed
2019-11-01 17:25 c_schmitz Category Survey design => Survey editing