Shows Members a Logged Out Page After Logging In

Better still, is there some way I can stop caching in the BBPress forums completely? I suspect the caching is causing another problem as well, where the “freshness” data is wrong, as if it’s showing an old version of that data displayed as well.

You can prevent a page to be cached with <!–[wpfcNOT]–>

I would really like to see a more versatile solution.

I have content on pages which only shows to logged in users. If a logged-out user is on one of these pages, and logs in, the page refreshes but is still showing as logged out, and they are unable to view the private content.

I see this has been discussed with W3TC.

// Fix W3TC Logout Issue
add_action('wp_logout', 'mj_flush_w3tc_cache');
function mj_flush_w3tc_cache()
{
    if (function_exists('w3tc_pgcache_flush')) {
        w3tc_pgcache_flush();
    }
}

Is a fix like this possible with WP fastest cache? Would be so cool ??

but it is impossible because logged-in users cannot see the cache version.

here is .htaccess rule
RewriteCond %{HTTP:Cookie} !^.*(comment_author_|wordpress_logged_in|wp-postpass_|wp_woocommerce_session).*$

Can you create a profile for me? I wanna test it.

Olly, I mentioned it in another thread, but I figured out the issue. It’s the browser cache settings that cause the problem. Logged in users are seeing the cached version saved in their browser instead of the cached version served by the site, which is why the setting to not show cached pages to logged-in users doesn’t work. Disable the browser caching option in WPFC and the login problems go away completely.

It’s not ideal because you lose some optimization. But perhaps you can manually tweak the browser cache timing to get similar results. If so, I hope you’ll share it here. Maybe then we could get the defaults tweaked so people don’t run into this issue. Thankfully the slow-down was minimal when I turned mine off (less than a .2 second decrease in speed, though mileage may vary).

thank you so much jhmattern ??

Thanks for the replies guys. Should have mentioned I had browser caching off, so that would be a separate issue.

Also didn’t mention I had “logged in users” unchecked, so as I understand it, it was the site’s caching (not the browser caching) that was causing the problem.

I have now checked the “logged in users” checkbox and this has solved the problem.

But it’s a shame site caching cannot stay on while a user is logged on. If the caching could be flushed as a user logs in, would that allow us to keep site caching on? (that way we would only lose cacheing for 1 page load)

Emre, I can set up a profile for you on the site, can I send you it in an email?

Many thanks ??

Yeah, you definitely need both of those settings — logged-in users checked and browser caching unchecked. I’m glad you got it working. ??

And I agree. It would be nice if browser caching could still be enabled for logged-in users. I don’t know much about it, flushing the cache on login would be great if it can be done. Either that or limiting caching to no more than a second for certain pages or sections of a site.

But it’s a shame site caching cannot stay on while a user is logged on. If the caching could be flushed as a user logs in, would that allow us to keep site caching on? (that way we would only lose cacheing for 1 page load)

Cached files are not removed. If a user is logged-in, the user does not see the cached version.

Emre, I can set up a profile for you on the site, can I send you it in an email?

[email protected]

It would be nice if browser caching could still be enabled for logged-in users.

It is already like that. Browser caching does not depend on “logged-in”.

Nice one, emailing you. I think jhmattern meant site caching not browser caching?

as i understand it, browser caching is the site sending a cookie to the browser saying “cache these pages”. the cookie also contains information on when to expire the browser caching and request fresh pages (for example in a month or in 24 hours). once browser caching has been turned on there is no way for the site to disable it as it’s up to the browser, not the site.

once browser caching has been turned on there is no way for the site to disable it as it’s up to the browser, not the site.

exactly. You can find the browser caching rules on .htaccess.