• When I edit an existing page, the cache is not purging for that page (and it’s not purging the homepage or other archive pages).

    If I tell W3TC to purge the individual page, it will reload the page in the editor, and say that the page has been purged, but it has not actually purged–in an incognito window I’ll see that it’s still showing the old version, and have hit “Refresh” a few times to be sure it’s not my browser caching it. Disable the browser caching module entirely doesn’t help.

    I’m using Cloudways hosting/management on Digital Ocean, and am using APC for both Page Caching and Object caching, per their recommendation.

    Flushing the entire page cache works just fine.

    Page Caching via APC
    Minify via Disk (disabling makes no difference)
    Object Cache via APC
    Browser Cache (disabling makes no difference)
    CDN – Cloudfront

    My site is all-SSL, and I have “Cache SSL requests” enabled. In the Page Cache Purge Policy, I have every box checked.

    Any ideas? Thanks!

    https://www.ads-software.com/plugins/w3-total-cache/

Viewing 10 replies - 1 through 10 (of 10 total)
  • Thread Starter Andrew Wilder

    (@eatingrules)

    I just tried changing the Page Caching method from APC to Disk Enhanced, and sure enough it works properly now.

    Any ideas what configuration might need to change in APC to allow single-page purging?

    Thread Starter Andrew Wilder

    (@eatingrules)

    I just did a little more testing.

    It seems that the single-page purging does not work with APC or Memcached if the site URL is set to SSL (https).

    If the site domain is set to http it works fine (even if viewing the cached pages on https). But if the site’s domain is configured to https, it doesn’t seem to work.

    Is this a bug in W3TC?

    You should run page and minify cache from disk always. database and object are always run from apc or mem. That’s the best for performance.

    Thread Starter Andrew Wilder

    (@eatingrules)

    Thanks Destac, I appreciate the input.

    My web host (Cloudways) insists that APC is best for both Page and Object caching. Why do you say Disk Enhanced would be better?

    Hi. Has anyone found a fix for the issue described by Andrew Wilder? We have the same problem, we are set to memcached and have https, and individual page caching does not work.

    Thread Starter Andrew Wilder

    (@eatingrules)

    @macnmotion2 I’ve since switched to Disk:Enhanced for Page Caching, and it’s been working far more reliably than APC page caching did, anyway…and I can prime the cache more aggressively (and keep pages cached longer) without worrying about using too much RAM. I also like that if the server is restarted it doesn’t have to rebuild the cache… I know that’s not a solution, but it seems to be a good workaround anyway. ??

    Thanks. We are using memcached on our site, not sure what will happen if we change the page caching setting from memcached to disk enhanced. Will that no longer use memcached for our database caching? We can’t take a chance on breaking our database caching. Thoughts?

    Thread Starter Andrew Wilder

    (@eatingrules)

    Page caching and database caching are configured independently (Performance->General Settings), so I don’t think it would be an issue there.

    In my case, individual purge does not work even with disk cache. It’s pretty silly, but I have to delete _index_ssl.html manually…
    (The site is all-SSL)

    Thread Starter Andrew Wilder

    (@eatingrules)

    @tiv.NET INC. – That sounds like a file permissions issue. Is WordPress running under the same user account as your FTP account?

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Pages not purging when updated, or when single purge is requested’ is closed to new replies.