• Resolved +ES

    (@evelynmsdesigngraphicscom)


    Hello+

    I have several clients that host their sites with WPE – and I LOVE that! I especially like WPE’s “purge all caches” option (under WP Engine > General Settings) as this Purge Cache button works fantastically each and every time as expected.

    I have several clients that do not host their sites with WPE (I am trying to move everyone over there but some resist) and those sites are using a different plugin to purge/clear the cache — that one does not work as expected each and every time and has been quite frustrating. So, I was looking around and came across this plugin!

    I see that you have indicated that this plugin can work on sites not hosted by WPE. However, I would like to know if it will clear “all” caches (that the above mentioned button does) on the non-WPE sites?

    The ones I am particularly interested in are:
    Cache System
    Preload
    Logged-in Users
    Mobile
    New Post
    Update Post
    Minify HTML
    Minify Css
    Combine Css
    Combine Js
    Gzip
    Browser Caching
    Note: I have pulled the above terminology list from the frustrating cache clearing plugin.

    Thank you.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Ethan Kennedy

    (@ethankennedy)

    Hey!

    Unfortunately the cache purging functionality is specific to WP Engine, and the varnish cache there. The headers work on other hosts, but otherwise the stuff actually purging is specific to WPE.

    The functionality would be specific to the cache implementation and the functionality there. In varnish it can be purged by sending an http request to the backend with specific information. This can be written as a plugin and can be called with various hooks (new post is a specific on WP Engine uses). The others would really boil down to implementation more than anything.

    Last-Modified headers can help with browser caching, as long as your new posts update that last modified value. My plugin does do this on any host.

    Browser cache for statics is tricky, but version tagging them is a good solution there. This will change the URL, so it’ll be a whole new object for the browser to cache, and will force the browser to pick up the new content. Here is a good post about it https://www.theasta.net/blog/2014/11/04/Versioning-JavaScript-and-CSS-files-while-improving-page-load-time/ .

    Logged-In users generally shouldn’t be cached, but fragment caching is something worth looking into: https://css-tricks.com/wordpress-fragment-caching-revisited/ .

    I hope some of this information is helpful. If you do try out the plugin for last modified headers, let me know if anything behaves unexpectedly. The plugin is written and tested on WP Engine specifically, so I don’t have much insight on other hosts.

    Thanks!

    Thread Starter +ES

    (@evelynmsdesigngraphicscom)

    Hi+

    Thank you very much for the quick response and detailed explanation. I will check out the provided links and suggestions… Go ahead and close this thread and if I have any issues in my testing(s) I will open a new ticket.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Using this Plugin on Sites Not Hosted by WPE?’ is closed to new replies.