Hi,
As the title suggests. When we create surveys and publish them the "next" and "previous" buttons redirect the user to the admin section which requests them to log in.

I have tried using different templates thinking that it might have been some modifications that we made to the template, but even the default one breaks like this.

We are using Lime Survey 1.85.

Here is a link to the survey the-ec.com.au/ECConnect/index.php?sid=92314&newtest=Y&lang=en token is 123456

The link doesn't work, it says the survey isn't available.

Let's see how we can solve this:

1. What did you set as $rooturl?

2. Are there any .htaccess files at the limesurvey directory or the above folder.

3. Please switch on debug mode by adding the following line to your config.php file:
Are there any additional errors reported on top of the page?

4. Why don't you use the latest 1.90 version? 1.85 is really old!

I've since fixed this, at the time of posting upgrading wasn't viable for the project. But circumstances changed and I was able to upgrade to the latest 1.90 build which fixed the issue.

I'm not sure if this will happen for anyone else, but

1. $rooturl was the base directory for limesurvey (in this case /ECConnect

2. There wasn't any .htaccess files affecting the limesurvey directory

Thanks for your help.

Some webservers cause problem when not taking care of upper-/lower case folder names correctly but in this case it seems to have been a different issue.

Check your template (especially conditions and progress bar). Customized templates might get a little buggy when updating from such an old version to 1.90.

Yeah I thought that might be the case, but it was weird. We originally upgraded to that version of LimeSurvey from an old version of phpsurveyor.

After the upgrade everything worked properly. I was able to bring forward the previous template without any dramas. But it just kind of stopped working so we were at a loss of what else to try.

I had tried using the other installed templates. I did think that it might have been the customisations that I made which broke the next/previous functionality but it was affecting every template.

Thanks for your feedback. Luckily you could solve the problem.