Will try to reproduce

Hi,

If I understand correctly, your steps are:

• Set 'Allow multiple responses or update responses with one access code' --> On
• Add a participant
• Set 2 as a value to Uses left
• Fill the survey three times
  Uses left shows -1.

The expected would be to have uses left to 0 and only allow 2 times, right?

This setting is always tricky :)

'Allow multiple responses or update responses with one access code:'.

This refers that:

• If token persistence is Off, by checking the checkbox you will allow multiple responses with the same access code.
• If token persistence is ON, by checking the checkbox you will be able to update the responses with the access code.

https://manual.limesurvey.org/Participant_settings/en#Allow_multiple_responses_or_update_responses_with_one_token

I agree this UI could be enhanced. With a bit of JQuery, the proper texts could be set in place depending on which prio option is checked.

There are several places where more dynamic GUI would be nice. For example, if 'Show welcome screen' is Off, then the page 'Survey text elements' could show an info text about this in Description-field.

But this is somewhat different. Why can't there be an option where a participant could change his/her answer, but not make another answer?

And in any case, if I set 'Uses left' to 2, I suppose the participant can answer 2 times.

Why can't there be an option where a participant could change his/her answer, but not make another answer?

That's the case when If token persistence is ON, by checking the checkbox you will be able to update the responses with the access code.

And in any case, if I set 'Uses left' to 2, I suppose the participant can answer 2 times.

I agree that setting may not make much sense if you set token persistence to ON

Confirmed this behaviour, which is not as expected.
https://bugs.limesurvey.org/view.php?id=18315#c73296

OK, current behaviour is as follows.

If token persistence is Off, by checking the checkbox you will allow multiple responses with the same access code.

This allows infinite responses. Uses Left field is not honored.
This field is only honored when "token persistence" is Off and "allow multiple responses with the same access code" is Off

So, my conclusion is we should update a bit the GUI to:

• make the text dynamic and change according to previous checkboxes
• update the texts to be more clear.
• update the manual

@c_schmitz thoughts?

@gabrieljenik I agree that this definitely needs clarification, so I agree to your proposal.

Jquery screen rules for "Allow multiple responses or update responses with one token":
1) If:

• the survey is anonymous or

• "Enable token-based response persistence" is set to "Off"

  Then:

• Make the label "Allow multiple responses with the same access code"
• Show a help text (or similar) that says "Participants will be able to enter as many responses as they want, despite what 'Uses Left' token attribute is set to."

2) If:

• the survey is NOT anonymous and

• "Enable token-based response persistence" is set to "On"

  Then:

• Make the label "Allow to update the responses using the access code"

https://github.com/LimeSurvey/LimeSurvey/pull/3010

As an improvement: persistence could be turned off automatically if the anonymous responses option is ON, to make it clearer for the user.

As an improvement: persistence could be turned off automatically if the anonymous responses option is ON, to make it clearer for the user.

:/ unsure on this point, just leave it like this since. It's not a good way to do something without user action.

1. You check persistence to ON + Anonymity to OFF
2. Save
3. By error : Anonymity to ON
4. Fix your error
5. persistence is OFF but you don't see it.

New PR: https://github.com/LimeSurvey/LimeSurvey/pull/3060/files
Had to do a new PR as for easier merging

Fix committed to master branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=35340

Tested and merged.

Fixed in Release 6.2.2+230814

@tibor.pacalat This could probably be a good candidate for re testing. By comments, it could have been got lost or got broken

On 6.6.8+241104 I still got Uses left -value go to negative number.