- Posts: 5
- Thank you received: 0
Can't regenerate question codes
we have a problem with the Regenerate question codes feature. Whenever we try to use it on an inactive survey (doesn't matter if straight or by question group), we are being redirected to the survey index and the question codes remain unchanged. The problem likely lies in our installation and/or server configuration, seeing as the feature in question works flawlessly on a separate LimeSurvey installation hosted by LS.
One of our devs tried to figure out where it went wrong and discovered that the regeneratequestioncodes action isn't called at all when using the regenerate feature (no difference between running it normally and using die() at the top of the action). The index action is called instead which then redirects us to the survey index.
Do you have an idea how this issue could be solved or where we should look next to find the cause of it?
msuelzer wrote: Do you have an idea how this issue could be solved or where we should look next to find the cause of it?
The Demo.limesurvey.org Version 2.64.0 is showing the same behavior as you described. Redirection to the survey list.
What version/build is used with your LimeSurvey hosting with LimeSurvey GmbH?
How it is possible that the same version is having different code (one with the bug, one without the bug).
msuelzer wrote: The hosted installation runs on Version 2.63.1 as well.
Is the hosted installation not the same as the downloaded version when it comes to version/build?
Which would mean that msuelzers issue won't necessarily be fixed since the Yii config isn't changed on the selfhosted installation with your fix.
olle wrote: How Yii constructs the URLs depends on the config, which might explain the problem.
The fix contains just adding sa in a path.
Or the versioning is getting more confusing.
The demo.limesurvey.org is stating version 2.64.0 and the regeneration of questioncodes is now working.
The release 2.64.0 Build 170307 is three days old.
What was changed at the demo installation then?
I can confirm that it has been fixed by upgrading to Version 2.64.1; editing the config file manually wasn't necessary (though as you wrote, fixing it manually would've been trivial as well).
jelo wrote: Which would mean that msuelzers issue won't necessarily be fixed since the Yii config isn't changed on the selfhosted installation with your fix.