Have you checked the Anonymous user role (or whatever role you assigned to the anonymous user) to see if all data is still valid? Specifically, check the <b>user/login</b> permission. If the limitation says <b>SiteAccess()</b>, it's become invalid. Edit the policy and reselect the right siteaccess.
I've seen this happening in a few cases when upgrading to 3.6.5 or 3.7.3, but I haven't been able to pinpoint the exact problem. I suspect the new 64bitCompatibilityMode, although I'm not even 50% sure.
I found the issue and it is indeed somewhat that Hans pointed out. It's not the siteaccess however that's compromised, but it is the content part that incorrectly points to the section instead as to standard. As soon as i changed it, everything was fine.
If this is a bug Hans and you haven't filed it, I will file it as a bug as the behaviour indeed is not as expected.
Thankx for the input Kris and Hans.
You must be logged in to post messages in this topic!