Hi guys,

I recently set up a survey on Build Version 3.15.1+181017 and when I try to set a redirect on a quota I'm experiencing some odd behaviour. Normally, when Autoload URL is not ticked, LimeSurvey will show the default quota message with the URL redirect below it. The link doesn't show for me now, unless I type in the description.

The main problem: when the survey should automatically redirect the user, it is just refreshing the page and clearing all answers.

Updated build to Version 3.17.16+190906 and the issue still remains

Setting a redirect on completion of survey works fine.

Setting a URL on any quota is ignored by LimeSurvey and just refreshes the current page if met during a survey

What kind of template do you use? If it is a custom one, try with one of the standard templates.

Switch Ajax-Mode off.

Export your survey as LSS and upload it here so we can test it. Or import it into the demo to see if it works there.

Hi Holch, it is an extension of Bootswatch (only custom.css edited) and brandlogo uploaded.

Running it through some devtools shows the below error -

Source map error: Error: request failed with status 404
Resource URL: example.org/tmp/assets/fb768dfb/pjax.js
Source Map URL: pjax.js.map

Disabling Ajax-Mode resolves this issue, but affects the template design.

Disabling Ajax-Mode should not have an impact on the template design, in my opinion.

What happens when you use the standard (not modified) bootswatch template?

Disabling Ajax Mode on bootswatch templates seems to stretch the main questions container until the browser cache is cleared.

The unmodified Bootswatch template works okay, and all files in the non-working templates show as inherited from this. The only difference in templates is the custom.css and a different brand logo.

Is there any way to avoid needing to disable Ajax Mode here, given the error (ajax/pjax map file 404)?

In my opinion, the Ajax Mode should never be on. It is one of the main sources of issues currently. For the next version of LS it will be switched off by default, as far as I recall.

The unmodified Bootswatch template works okay, and all files in the non-working templates show as inherited from this. The only difference in templates is the custom.css and a different brand logo.

So obviously some of your changes in the custom.css lead to this problem.