• Frank

    (@frankvancaspel)


    I have a few questions about how the ‘never cache the following pages’-function works.

    1. If I want to exclude http://www.mydomain.com/page from caching, I enter /page in the entry field, correct? Or should I enter /page/, or doesn’t it matter?

    2. If I enter /page in the exclusion field, and I have another page which’s name also starts with ‘page’, say /page2, will that page also be automatically excluded from caching if I enter only /page? That is wat seems to be implied in this topic.

    3. Are private pages cached? It feels like they will not, but I can’t find any settings or documentation for it.

    Thanks!

Viewing 3 replies - 1 through 3 (of 3 total)
  • Not answering you’re question, but I’ve found on one of my sites (which use apache) it won’t work if I put /page , rather I have to remove the slash so it’s just page , whereas on my other site (uses nginx) it works with /page

    As for your question, you can easily answer it yourself by some testing. Visit those pages on another browser (which is not logged in wp, clear cache to be safe) and check the timestamps at the bottom of page source as your refresh it a couple times, they should change on each refresh if they are not cached.

    Thread Starter Frank

    (@frankvancaspel)

    Thanks Virendar! Using the page source I was able to ascertain which of my pages are currently being served from cache, and those that I’ve specified in the ‘do not cache’ field aren’t, which is good. Also: private pages do seem to get cached.

    I have one more question though: the reason I’m trying to exclude one of my pages from the cache is because it has a form on it, which is made using the plugin ‘Visual Form Builder‘. Unfortunately, that form stopped working after (but not directly after) I installed W3 cache, and the maker of the form-plugin suggested (in this topic) that this may be because the security check of the form uses a nonce which gets outdated when the cache ages. Do does anyone know if there is a way to still cache this page without braking the form?

    Incidentally: I’m not sure that the caching caused the problem in the first place. I’ve now had a cached page with the form up for more than 24 hours, and the form still works. This looks like a good thing, but it does mean that I don’t know why the form broke in the first place…

    Only fragment caching would allow you to have your cake and eat it too, but the page would still load slower. I suggest using WuFoo or similar imho.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘[Plugin: W3 Total Cache] Questions about 'never cache the following pages'’ is closed to new replies.