-
- 225 Posts
Maybe this is normal, but it appears a little odd.
I have a client’s site that I built some time ago. They are running Evo and WebLoginPE (both up to date). The login form is accessible from a link that takes you to a separate page w/ the form. In Firefox, I can login in and select "forever". From there I can kill the browser and come back later and still be logged in (like expected).
In ALL other browsers, I will still be logged in. However, when I click on a link to a secured page, I get redirected to the custom error page for secured pages (as if I wasn’t logged in). However, if I click the link to the login form, it will show me as logged in and I will then have access tot he secured pages.
So basically, when I re-open the browser (while already logged in), I still have to go to the login form page to gain access to secure pages.
This is all very trivial to me. But for some reason, my client decided after 2 years, they don’t like this behavior.
-
- 225 Posts
I guess I could try to add the Personalize snippet, which should force the system to check login status?
Are you going in to the site with the same URL? Particularly www.domain.com and domain.com are treated as separate domains, and a login to one URL won’t be logged in to the other. I try to always have an .htaccess rule to force all requests to one or the other.
-
- 225 Posts
I was originally hoping that was the issue, as it is an easy fix. However, it’s not the issue. Thanks for the help though.
-
- 225 Posts
I added the personalize snippet and it was no help. The logged in message only shows after I go to the login form page, which is the same behavior for accessing the secured pages.