Thread

It appears the issue discovered in this thread, is also a problem in ee 1.6.9:
http://ellislab.com/forums/viewthread/149815/

If auto log-in for future visits is checked, in Safari, the log out link doesn’t work, I just get redirected back the CP home and am still logged in.

In my testing, it appears, like the thread above, to only be a problem in Safari/Webkit, and only on sites that I’ve upgraded to 1.6.9. Older sites seem to work fine, even in Safari.

Even more confused now…I found a 1.6.9 (same build 20100415) site where the logout works.

The only other commonality with the 1.6.9 ones that aren’t working vs 1.6.9 one that is, is that the broken sites are running their system folder above webroot. Could this possibly have something to do with it?

In all cases, the sites are using a masked CP.

More info: I previously thought this to be isolated to Safari, but I just experienced the same in Firefox 3.6.8, so there goes that theory.

Update: I tried moving the system folder above webroot for the site that worked, and it still worked.

Totally lost :(

Hi timkelty,

Are you removing index.php from your URLs? Please try temporarily renaming your .htaccess file and set ‘index.php’ back as your index page before we troubleshoot further. Any change?

Tried that with same results…I went through the mentioned thread and tried anything mentioned, pretty much

Does it work when you’re using session ids? In other words, is the issue restricted to cookies only?

Ok for CP login:

* If I change to cookies + session, I can log in, logout works, but then if I try to log in again, nothing happens. The login page just reloads. It will continue to do this until I clear my cookies.
* If I change to session only, login/logout seems to work as expected
* With cookies only, I can’t log out.

Beginning to narrow things down…

I had removed my htaccess when testing earlier, but apparently hadn’t cleared cookies and logged out, which apparently affected it.

It seems to boil down to this rule:
ErrorDocument 404 /index.php?/pages/404

If I remove it and clear cookies, everything seems to work. I noticed that after I click logout and it doesn’t work, my exp_tracker cookie has a💯{i:0;s:11:"/pages/404/";} as its value.

Strange things is, on the install I have where everything works, that exact same htaccess rule exists.

I know you don’t support htaccess stuff, but if you could point me in any direction that would be great.

Hi timkelty,

Glad you narrowed it down. We’ll probably need to shift over to the CodeShare Corner for discussion on server configuration, but before we do that, why not let EE handle your 404s?

Wow, solved.

First off - to answer your last question, I do let EE handle them, but that htaccess is to send people the ee 404 for urls ee doesn’t process (/assets/styles/thisfile_doesnt_exist.css).

Here’s what happened:
I had a cp stylesheet included via LG Add Sitename that referenced an background image that wasn’t there.
That resulting 404 is what was borking the logout!

I don’t totally understand why. But things make more sense now, so I’m happy.

Hi Tim,

Glad that you got this issue resolved.

Cheers

Greg