Most browsers not working (except Firefox). jQuery related issue
I am running my study on mindprobe. I can't load my study on most browsers (except Firefox).
When I click the jquery link, I get this error message:
Requested page /publix/81808ee8-7465-46a5-a7ce-88b0ad5c8b18/57ff7de9-e1e6-4c5c-9623-81763538239c/jatos-publix/javascripts/jquery-3.5.1.min.js couldn't be found.
Is this an issue with jquery? If so, how can I fix this?
Comments
Hi @Sigmund ,
This seems to be an issue with the JATOS server being unreachable, so I moved this to the JATOS category. Are you running this on MindProbe.eu or another JATOS server?
@kri Do you know where this error comes from? I've seen this error reported by someone before, but don't understand where it comes from, and never experienced it myself.
— Sebastiaan
Check out SigmundAI.eu for our OpenSesame AI assistant!
Hi Sigmund!
That seems to be a caching issue with your browser / JATOS. Mindprobe got updated recently to the latest JATOS version and the latest jatos.js uses the latest jquery library (3.7.1 instead of 3.5.1).
I see three possible solutions:
1) You can add the following in your HTML, in the <head> section:
2) You can change the line in your HTML, in the <head> section, where the jatos.js is loaded and add a
?v=3.9.1to the filename:3) You could also just wait. Browser caches invalidate after some time (hours or days - it's difficult to actually find the cache invalidation time span for a certain browser and its version). Chances are that it is already working again in your Firefox.
Now that I'm thinking about it: the second solution is probably the best one, because it forces the browser to only fetch the latest jatos.js and still retrieves the other files from its cache, which would save a little bandwidth and reduces loading times.
Best,
Kristian
Hi Sigmund!
I actually looked a bit deeper into this issue today and found that under some circumstances the reason that jquery cannot be found is not the browser's cache fault but lies on JATOS' side. I'm investigating further.
Best,
Kristian
Hi Sigmund!
The fix is part of the release v3.9.2.
Best,
Kristian