I have a home page which changes content based on whether the user is logged in or not.
The primary difference in the
non-authenticatedviews is that the non version shows no main header (using the
If I am logged out, everything displays as it should. When I click the login link and authenticate a user account, I am directed to the dashboard (as expected). I then click to view the site and am shown a cached version of the homepage containing the non-authenticated view. Doing a hard refresh resolves the issue. If W3TC is disabled, all issues go away.
It’s clearly caching the queries to the DB that are generating the menu, etc, but how do I stop it? I have explicitly disabled home page caching, but that seems to only be relevant to some content. I’m not sure if it is relevant, but I am developing a child of the Responsive theme.
The following is the W3TC documentation from the bottom of the home page after logging in (where the wrong content is loaded):
<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/ Page Caching using disk: enhanced Database Caching 27/55 queries in 0.180 seconds using disk: basic Object Caching 1130/1248 objects using disk: basic Served from: sbirgps.org @ 2013-02-13 12:59:31 by W3 Total Cache -->
- The topic ‘Home Page is Caching When It Shouldn't’ is closed to new replies.