I have an application that is a dashboard for a bunch of LimeSurvey surveys where users can select their group and take the relevant surveys. The app uses the LimeSurvey API to add a participant to the table and generate a token for them, then include the token in the link for the user. It is formatted as follows:

somewebsite.com/limesurvey/index.php/331...oken=K10D6OI0r3bgZXg

On the production server, when the link is clicked it simply starts the survey as expected. However on the staging server, it leads to a page saying "If you have been issued a token, please enter it in the box below and click continue." and a field for the token. This can be worked around by simply copying the token from the url into the field and submitting the form, but ideally this should work the same as the production server.

Additionally on the staging server, there are issues with the pagination not working in the list surveys page, as well as I get an alert saying "An error occurred while processing the ajax request." when I try to add a subquestion to an array questoin. These issues do not happen on the production server. I would also like to resolve issues, but the issue with the token is more important to me.

Both the production server and the staging server are running Version 3.5.4+180320. The database on the staging server is an import of the one from the production server. The code for the application that links to the LimeSurvey surveys is also identical. I have tried everything from reinstalling LimeSurvey on the staging server, upgrading LimeSurvey to Version 3.24.1, copying the files from the production server to the staging server, consulted the docs to make sure I haven't missed a step, Googled the problem and searched the forums for hours to no avail.


Any help with this would be very much appreciated.

Are the links on both servers the same? currenlty my first guess would be that LS doesn't recognize the &token in the URL.

E.g. the position of the &token within the URL.

So maybe the newtest or the &email is "blocking" the token from getting recognized?

Yes, the link structure is identical. I've removed the additional parameters so it's simply /limesurvey/index.php/331328?token=K10D6OI0r3bgZXg. This allows me to access the survey on the production server fine, but I still hit the token page on the staging server.

Compare the native links for each installation (click on the preview survey buttons). There are config settings that may, for example, remove "index.php".

My opinion : 2 issues with GET param in url (token and pagination + some ajax issue) :! issue in server.
Some «security» in URL ?

Must check server log, not related to LimeSurvey.

tpartner: I double checked and native links are identical.

DenisChenu: That is an interesting point. I'm not sure how the server is set up, but I will look into this and let you know what I find.

DenisChenu was correct. It was an issue with the server configuration. I was missing the ?$args in the try_files line:

location /limesurvey/ {
try_files /$uri $uri /limesurvey/index.php?$args;
}

Thank you all for your help with this.

Ah you use ngynx with rewrite ⋅ i have a doc issue to fix it

bugs.limesurvey.org/view.php?id=14691

manual.limesurvey.org/General_FAQ#How_ca...to_get_a_shorter_URL

I muts create the complete page for ngynx …