Support » Plugin: W3 Total Cache » [Plugin: W3 Total Cache] W3 total cache for logged in users

  • Hello,

    (Sorry for my approximative english)

    I’d like to use a cache plugin for logged in users, because 70% of my trafic is users who are logged in (it’s a private buddypress community).

    However, we know the problems which appear when we do not check “Don’t cache page for logged in users”, some visitors see content normally reserved to logged in users.

    To solve this problem, we made an exclusive part of our website only for logged in users : I mean that visitors can’t see this part if they are not logged in, they only see the homepage which is a landing page.

    The problem is that if a non logged in user know the URL of some logged in reserved parts of the website, he can see this content because it’s cached, even if this content is private.

    Is there a way to tell to W3TC to respect the private conditionnal statement, and to not allow the logged in content to be viewed by visitors, even this logged in content is cached for logged in users ?

    Another question: is it possible to tell the Database Cache to never cache the following pages: (view/72, etc…)

    The main goal is to improve performance of a buddypress installation.

Viewing 3 replies - 1 through 3 (of 3 total)
  • In other terms, could we have a separate cache: one for the logged in users, and one for the logged out users? And to prevent W3TC to cache some user private content (messages, personal settings, edit profile page, etc) ?

    Then, is there a way to flush the cache after user edit profile ?

    Don’t know if you have solutions to suggest me, but in the meantime, I’ve solved a major part of my problems by using fragment caching, it seems that everything is working fine now 🙂

    Plugin Author Frederick Townes


    Unfortunately it’s not as simple as 2 caches, each user would need their own cache.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘[Plugin: W3 Total Cache] W3 total cache for logged in users’ is closed to new replies.