by
KK » Thu Mar 31, 2016 1:34 am
Thanks.
I checked and found that the problem was occurring only with the index.php template.
The access permissions were fine and it was also not a prettyURL issue so it was a bit intriguing to find that only super-admin could access the template.
It came to my mind that this behavior (by design) is also seen in non-executable templates so perhaps the template was set with
executable='0' using the <cms:template> tag.
As it happens, the <cms:template> tag was not being used at all in index.php.
Now, it is possible that at some time during the development you happened to use this tag and set the 'executable' parameter to '0'. Then later on you removed this tag from the template.
Just removing the tag wouldn't reset the executable param back to '1'.
So, I added the following explicitly to your template -
- Code: Select all
<cms:template executable='1' />
Visited the changed template as super-admin and then logged out to check if it worked.
And, yes it did.
So, there you have the solution