Reading query params from the URL

[alpkaanaksu]

Hi Ruben,
what is the best way to access the query params from the URL?

e.g. https://formr.instance.com/run?message=hey

How can we access the character value "hey"? How can we save this information permanently? (so that we can write something like params$message and get "hey")

[alpkaanaksu]

I think I found it here: https://github.com/rubenarslan/formr.org/wiki/How-to-collect-an-ID-(Mturk-Prolific-etc.)-from-the-URL

[alpkaanaksu]

@rubenarslan Ok, it kind of works with the get param type, but as soon as we click on a submit button, or go to next page, the page reloads and we are in a new session, the URL is the run base URL without the query params.

[rubenarslan]

The value of the get parameter should be stored within the survey table at that point. Not so?

[alpkaanaksu]

They are saved in one of the sessions, but then we are in a new session somehow

[alpkaanaksu]

It works at first, but as soon as I click on submit the page reloads instead of going to the next page, and I get an error:

[rubenarslan]

Please make a reproducible example, ie a minimal run with a survey showing the problem.

…

On Thu 20. Jun 2024 at 15:04, Alp Kaan Aksu ***@***.***> wrote: It works at first, but as soon as I click on submit the page reloads instead of going to the next page, and I get an error: IMG_169CDF18000A-1.jpeg (view on web) <https://github.com/rubenarslan/formr.org/assets/68744864/50a1b832-3cee-448f-80b5-c023743202cf> — Reply to this email directly, view it on GitHub <#558 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGK5BIT6LJCMUWEGBAQD5TZILHNPAVCNFSM6AAAAABJTWWGHGVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TQMRYHA4TS> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[alpkaanaksu]

We couldn't create a minimal run because it works when we create a new run with a shortened version of the survey. I tried duplicating the run (by exporting and reimporting) and now it works in the new run. Very strange behaviour... But it works now (but only in the new run) 🤔

[rubenarslan]

That's odd. Try clearing cookies for the formr subdomains on your instance or opening the run in an incognito tab. That should not be necessary, but if this helps, I'll have an idea about how to keep this from recurring. The problem wouldn't affect your participants in that case though.

[alpkaanaksu]

I was doing all of this in incognito mode, so it was not a problem with the browser cache.

We were trying to access the run on formr.osc.lmu.de instead of on surveys.osc.lmu.de, so after opening the page, we were directed to surveys.osc.lmu.de. This is probably a thing with the configuration of our instance. Now it is working

[rubenarslan]

If you were doing all of it an incognito tab (including editing the run), there could be a complication. Yes, studies are logically separated from the admin area on your instance. The link to the run displayed is with the surveys subdomain. Access to the run from the formr subdomain should be blocked, but I see that it isn't. I'll check it out.