I just tried multiple browsers and had the same issue. When I go to motoringalliance.com and login... After the redirect, it seems like the session isn't passing a 'logged in' status to the box underneath the logo. It asks you to sign in and also give you the floating box. Opera 10.61 FF 3.6.8
I have the same poblem and even with a lot of help from Nathan I can't fix it. I scroll down to the bottom of the log in page and click on "contact us". When the page changes I am in and can get around just fine. Jim
It seems as if cookies are getting stuck sometimes on the user side. Most have been able to fix this by clicking Log Out making sure you get a message the cookies have been cleared. The next step is to clear cookies and cache in the browser. Close and restart the browser, then log back in.
I also get that from time to time and just hit forums from top menu and once it loads I'm shown as being signed in.
Yeah I mean I work in software support, I cleared out FF, but still I would be curious to see what was causing the cookies to fault? Curiosity killed the cat, and I am interested why.
I've been told it is a possible combination of using litespeed and the 60 min keep alive. Instead of Apache the M/A server is using LiteSpeed for it's lower overhead and greater speed. In addition I'm about to implement the PHP LiteSpeed SAPI to use a PHP version that is optimized for LiteSpeed. Testing has shown a 12% gain in speed when processing complex PHP operations on my test site over PHP 5.2.12. The site also has a 60 min time out time. Why 60 over the default 15? There are a few members that write longer articles and they were having time out issues when crafting them. What may be happening is when a member pops on and off the site multiple times the cookies start having conflicts. Logging out and clearing cookies often fixes this conflict especially if one is using multiple PC's, Mac's or other devices.
And that will accomplish what? As it stands now as long as one is active and moving around the site the time out does not come into play. Leave the site with logging off or just leaving a page open for 60 min and the session ends. Adding a notification that the session is about to end only complicates things and I'm not sure it adds anything to the user experience.
I wouldn't think there would be a large benefit either I just thought you might benefit from ending user sessions by t/o and resolve the session issue. And I thought with the alert at least the users creating long write ups wouldn't have an issue getting kicked off. Just trying to help
just happened to me as well (like 6 times lol). After finding this thread, I went to the 'Contact Us' link at the bottom, and then it was fine...logged right in