roguecomet

Someone savvy on the subject of the COOKIES used by WP during an admin session. The error discussed here occurs in Firefox, Chrome, and IE on, it seems, Win-platforms only.

I now realize I only have to shut Firefox down to end my session in the admin panel, ie. I don’t need to manually empty the complete cookie cache.

So for me the sequence is,

1 Start firefox, login to WP Admin panel – no problem
>>> several cookies created by WP in the cookie cache

2 I try to logout – the reset error occurs, and if I browse to my blog I can tell I’m still logged in because the ‘edit’-function on each post is active

3 I shut down firefox

4 I restart firefox, and check cookie cache:
>>> all cookies from WP are cleared except one

And browsing to my blogs I’m now logged out from the admin panel.

I should add I never saw this error before, all things being equal; same blogs, db:s, browsers, my OS – only difference is I’ve moved my blogs to a new host and suddenly this error occurs, so either it’s server related or something goes awry when you move wordpress files between hosts. But this is the only error I get so far – beyond the logout-error the blogs run fine, they display all content ok, and the admin panel works for common tasks – except the darn logout!

Anyone experimented with tweaking permissions for the WP folders/files? Could this have anything to do with it?

Count me in. Same problems. Host is Fatcow. What is peculiar is the support there view a different querystring hiding under the log out-button.

When I view it on my machine the log out link ends:
…/wp-login.php?action=logout&_wpnonce=2f823aa8fd

and I get the error trying to log out. When they (fatcow support) view the dashboard from their side, the same page on the WP dashboard has generated the alternate version of the button link: …/wp-login.php?loggedout=true

weeeeird!

Common jpegs uploaded into the Media Library. And all shown fine by Firefox and other image apps. But, to repeat, intermittently the blog page won’t show the image, or show it as ‘corrupt’ and only an emptying of the cache will resolve the issue.

So the sequence of events is
1 Uploaded pic shows ok and proves it not corrupt
2 Revisiting the page, the same pic does not show at all – only its caption – or image is shown in a ‘corrupt’ fashion – refreshing the page does not restore image
3 Emptying the Firefox cache resolves the problem
4 Problem resurfaces at Xth revisit later on

Have now occured also in IE. And only in the context of the blog. The physical files on server are not corrupt; they display fine on a static html-page or in any other app capable of handling jpegs.