Automatically empty proxy cached content when your site is modified.

Proxy Cache Purge

This plugin does not install nor configure a cache proxy. It acts as an interface with such services.
One common method of caching content for websites is via the use of reverse proxy caching. Common examples of this are <a href="https://www.varnish-cache.org/" rel="nofollow ugc">Varnish</a> and <a href="https://www.nginx.com/" rel="nofollow ugc">Nginx</a>. These systems allow a website to update content and have the visitor&#8217;s experience cached without the need for complex plugins storing the files locally and using up a user&#8217;s disk space.
A reverse proxy cache is installed in front of a server and reviews requests. If the page being requested is already cached, it delivers the cached content. Otherwise it generates the page and the cache on demand.
The Proxy Cache Purge plugin sends a request to delete (aka flush) the cached data of a page or post every time it&#8217;s modified.
<h4>How It Works</h4>
When content on a site is updated by WordPress, the plugin reaches out to the proxy cache service with the URL of the page, requesting the cache be deleted.
Not all page are deleted from the cache on every change. For example, when a post, page, or custom post type is edited, or a new comment is added, only the following pages will purge:
<ul>
<li>The front page</li>
<li>The post/page edited</li>
<li>Any categories, tags, and/or custom taxonomies associated with the page</li>
<li>Related feeds</li>
<li>Associated JSON API pages</li>
</ul>
In addition, your entire cache will be deleted on the following actions:
<ul>
<li>Changing themes</li>
<li>Pressing the Empty Cache button on the toolbar</li>
</ul>
Plugins can hook into the purge actions as well, to filter their own events to trigger a purge.
On a multisite network using subfolders, only network admins can purge the main site.
<h4>Development Mode</h4>
If you&#8217;re working on a site and need to turn off caching in one of two ways:
<ol>
<li>Add <code>define( 'VHP_DEVMODE', true );</code> to your <code>wp-config.php</code> file</li>
<li>Go to Proxy Cache -&gt; Settings and enable debug mode for 24 hours at a time</li>
</ol>
That will break cache on page loads. It is not recommended for production!
<h4>WP CLI</h4>
Purge
Purge commands let you empty the cache.
<ul>
<li><code>wp varnish purge</code> &#8211; Flush the cache for your front page</li>
<li><code>wp varnish purge [&lt;url&gt;]</code> &#8211; Flush the cache for one URL</li>
</ul>
You can use the parameter <code>--wildcard</code> to empty everything from that URL down. So if you wanted to empty cache for all themes, you would do this:
<ul>
<li><code>wp varnish purge https://example.com/wp-content/themes --wildcard</code></li>
</ul>
Debug
Debugging can help you figure out why your cache isn&#8217;t working as well as it could. The default is for your home page, but you can pass any URL on your domain.
<ul>
<li><code>wp varnish debug [&lt;url&gt;]</code></li>
</ul>
Available parameters:
<ul>
<li><code>[--include-headers]</code> &#8212; Include headers in debug check output</li>
<li><code>[--include-grep]</code> &#8212; Grep active theme and plugin directories for common issues</li>
</ul>
DevMode
Development mode allows you to disable the cache, temporarily.
<ul>
<li><code>wp varnish devmode [&lt;activate|deactivate|toggle&gt;]</code> &#8211; Change development mode state</li>
</ul>
<h4>Privacy Policy</h4>
As of version 5, this plugin no longer uses any remote data.

Alternative Plugins for

Discover the Lists with Proxy Cache Purge

Maintenance, Speed & Optimization

07.SpeedUp

Blog 2

namaroopa before migrate

vol intsall

startup

Maintenance, Speed & Optimization

Credit Platform

Maintenance, Speed & Optimization

exp