[Plugin: WP Super Cache] Logged in but actually not

You should try the debug system in the plugin. Limit it to your IP address and log to a file that you monitor when you load a page. It will tell you what the plugin is doing.

I have this same issue. We display a message in the header of most pages stating something like “Dear ${username}, you are logged in. Log out here.”. When I log out it still displays this, even though it did log me out.

I tried the debugging and that hasn’t helped me.

If I do a shift refresh (hold down shift while doing a refresh) it fixes this. So this might be browser cache related. But we can’t expect typical end users to do this.

Any ideas?

dspilka – odd, sounds like the browser is caching the page. Does anything else on the page indicate that you’re logged in (like edit links on posts)?

Sorry for the late response. Yes, there are other things on the page indicated I’m logged in. The edit links on posts show up and with the newest WordPress, the admin bar atop the page still shows.

I’m not sure what to try/do.

Have you updated to the latest version of supercache or tried the dev version?

This is with Super Cache Version 0.9.9.8, set not to cache for known users. I have not tried the dev version.

How do you create that logged in message? From the WordPress login credentials or some other cookie? Try using the debug system in the plugin to figure out what file gets served when you see this and why.

The logged in message checks the is_user_logged_in() function. The problem isn’t only with the logged in message though. As I mentioned above, the posts have their edit links and the admin bar shows like you’re logged in. I’ll keep trying.

I’m curious if the thread starter (Lunarll) is still seeing this or found a solution.

Use the debug system – it’ll tell you a lot about what cached page is being served. What you’re seeing shouldn’t be happening at all.

I everyone. I am having the same problem as dspilka. I’ll see what I can learn from the debug messages and update this thread when I’m done.

I had a look at the log and the cached page that WP Super Cache is serving. By the look of things, WP Super Cache has only cached the “not logged in” version, as expected.

It seems though that after clicking the “Log out” button, the web server returns a status code of 304, so the browser returns the version from its own cache. Could this behaviour be caused by WP Super Cache? I am doing this on a test server and have not set up and caching myself.

Yesterday I deleted the cache, this morning I’ve did a search in the wp-content/cache/supercache directory for pages that are cached when the user is logged in. It returned one result: a HTML page showing “Logged in as <username>”, so WP Super Cache does seem to be caching visits by known users, even though the setting says it shouldn’t.

The stats page says WP-Super-Cache currently contains 4746 Cached Pages, but WP-Cache contains 0 Cached Pages. It was my understanding that WP-Cache was meant to be used for known users. Is it not working correctly?

What can I do about this?

I checked the WP Super Cache log at the time when one of the files was created.

10:53:40 /2010/01/<article-slug>/ Output buffer callback
10:53:40 /2010/01/<article-slug>/ Anonymous user detected. Only creating Supercache file.

The problem is that the user wasn’t anonymous. What could be going wrong?

Something to do with cookies? Have you messed with them? There’s a function in wp-cache-phase1.php that checks the COOKIE array. Maybe debug that? Did the debug log report any cookie info found?

Thank you for your response.

I think it’s something to do with the Facebook Connect plugin that’s installed. It may not be setting the required cookies at the appropriate time when it handles logins. Their support isn’t as great – they’re not even on www.ads-software.com, but I’ve seen some user suggestions to use a WP Super Cache hook to set add cookies to be checked. I’ve been working on something to that effect since reading those comments. Apparently it’s a common problem so hopefully I can work it out. In your experience are there any alternatives that are known to work with WP Super Cache?