You mean when user enter token in the form. Because , i think it's OK if user enter with a link like token=myctoken&Q1=test

3. Open survey using that token
4. Manually add a get value to attempt to add a value to one of the two questions (adding '?SGQA=somevalue')

OK : When you do 3 : response are created, not updated after in 4. Then no update of current reponse.

You must copy/paste on a text editor before create the new responses.

Hi Denis

Thanks for looking at this. I'm not sure what you mean about using a text editor. If there is some confusion about what trouble I'm having - I'll try and give some more context.

I hacked together a "dashboard" of sorts to manage multiple surveys for users. From the dashboard, the user will click on links to their specific surveys (which are also tokenized, with the same token used on the 'Dashboard'). At the end of any given survey, the user is redirected using an end url back to their dashboard page. I send back one piece of data, which is the date of the completion of that particular survey. The user doesn't manually enter the data - limesurvey creates it using a combination of expression manager, pass thru variables, etc. I was only manually pasting for expediency. I don't believe it would make a difference if the link was directed automatically from limesurvey, or manually.

The end link formatting can be found below

http://your_server_address/index.php/PASSTHRU:returnSurvey?token={TOKEN:TOKEN}&newtest=Y&lang=en&{PASSTHRU:qcode}={date(%22Y-n-j%22)}

The problem I am having in 3.X versions, is that any get parameters listed (the qcode, in this instance, which is a passthru from the dashboard), are NOT then entered into the dashboard's fields. The 'qcode' in this case is the SGQA code for the field I wish to populate with the current time that the survey was finished.

I know this is an issue with tokenized tables, because I've tested the exact same method using a non tokenized survey with no trouble. And I utilize this method on a 2.x instance of limesurvey with zero issues.

I'm not sure if any of this helps, or if maybe I'm adding to the confusion.

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

Fixed, would be available from version 3.14.9.

@dominikvitt : can you check somewhere for your account on github to show your name in the message :).

Totally unrelated to any issue ;)

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

Fixed in version 3.17.3