Don’t Cache Page For Known Users

  • PurplePatchMarketing

    (@purplepatchmarketing)


    7 years, 1 month ago

    Hi there,

    I have installed WP Super Cache on a client’s website and enabled all the recommended features, including ‘Don’t cache page for known users’.

    I don’t know that much about caching, except that it is best practice to speed up a website, but I know that in the past, if you planned on making significant changes to a site (as an admin), you had to turn the caching plugin off, then make your changes, and then turn it back on.

    Is this “Don’t cache pages for known users” designed to avoid/replace this?

    In other words, can I tell my client that she can make edits to the content of her site without any need to turn WP Super Cache on or off, when she does so, since I have the “Don’t cache pages for known users” selected/checked/turned on?

    Please advise.

    Thanks in advance,

    Fiona

Viewing 4 replies - 1 through 4 (of 4 total)
  • jomo

    (@jonathanmoorebcsorg)

    Don’t cache pages for known users means that when known users are browsing the site, don’t add new pages they visit to the cache.
    This is useful in case the pages include some user-specific information.

    This is different and separate from the question of whether to show known users pages which are already cached.

    Thread Starter PurplePatchMarketing

    (@purplepatchmarketing)

    Thanks, @jonathanmoorebcsorg.

    However, I still don’t really feel like my question has been answered.

    Do I need to advise my client to switch the caching plugin off every time she makes changes to the site (and back on when she’s finished) – or can I tell her to just leave it on at all times and ignore it?

    Thanks,

    Fiona

    jomo

    (@jonathanmoorebcsorg)

    the answer to that question will not be related to the setting “Don’t cache pages for known users”

    In normal use, when you make changes to a post/page, the cache for that page is cleared.

    However not all references to that page may be cleared: for example if you change some attributes for a WooCommerce product, the page for that product should show the changes, however the product may also appear on many other pages in the product catalog / attribute archives etc and not all these pages may be refreshed.

    Depending on the characteristics of the site and your caching strategy, you or your client may not care about that.

    If you want to be quite sure there is never any out of date page, there is also the setting “Clear all cache files when a post or page is published or updated.”

    If the site is small the cost of rebuilding cache is not a big deal.
    If the site has 5,000 pages and it tqkes 1 second to rebuild each one, then you can calculate the impact that a rebuild can have..

    CmdrKeene

    (@shawnkeenegmailcom)

    Thanks for the details, now I understand that:

    1) Don’t cache pages for known users: If ON, known users won’t cause cached pages to get built as they browse around.

    2) Make known users anonymous so they are served super cached static files: If ON, known users will still receive a cached page if one exists.

    However in practice, #2, doesn’t seem to be working as I understand it to. If I’m logged in, the content at the end of the DOM does not show that it served a cached file or a date stamp of that cached file. It also doesn’t mention gzip compression.
    But if I logout or use incognito mode, I see both the timestamp of when that cached page was generated, and a note about gzip compression.

    Am I misunderstanding?

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Don’t Cache Page For Known Users’ is closed to new replies.

Tags