Brice Capobianco

Let you delete your posts revisions individually or all at once (purge or bulk action). Compatible with Gutenberg (experimental) and classic editor.
<h4>What does it do?</h4>
Simple Revisions Delete adds a discreet link within a post submit box to let you purge (delete) its revisions via AJAX. Bulk actions also available.
It helps you keep a clean database by removing unnecessary posts revisions. Unlike other similar plugins, it lets you delete only specific posts revisions, not all your site revisions at once. 
The plugin is perfectly integrated in the WordPress back-end, and uses native core functions to safely delete revisions. 
It is very lightweight, very simple to use, and just does the job!
<h4>How does it work?</h4>
The plugin adds a discreet link in the post submit box, next to the default revisions counter (see screenshots section). 
When you click on it, it will purge the appropriate post revisions via AJAX (no JS is also support). 
It also add a new bulk action option in the post/page row view to let you purge revisions of multiple posts at once.
<h4>What’s new?</h4>
Since v2 you can now purge all your posts revisions from within the Gutenberg editor. 
Keep in mind that this feature is experimental. I haven’t yet find any way to make it works in a proper way with the current block editor available methods. I’m using jQuery (and AJAX) which is pretty much a hack (a workaround) and not a clean method considering the langages using by the Block Editor.
Since v1.3 you can delete a single revision at once (see screenshots).
<a href="http://b-website.com/simple-revisions-delete-free-wordpress-plugin" title="Plugin page" rel="nofollow ugc">See plugin page</a>
NOTE: There is no admin page for this plugin – none is needed.
<h4>Post Types support</h4>
The default supported post types are post and page, but you can easily add custom post types or remove default post types with the following hook:
<pre><code>function bweb_wpsrd_add_post_types( $postTypes ){
 $postTypes[] = 'additional-cpt';
 $postTypes[] = 'another-cpt';
 return $postTypes;
}
add_filter( 'wpsrd_post_types_list', 'bweb_wpsrd_add_post_types' );
</code></pre>
See CODEX to add support to all CPTs: https://codex.wordpress.org/Function_Reference/get_post_types
<h4>Custom user capability</h4>
The default capability to purge or remove rivisions is delete_post, but you can override this with the following hook:
<pre><code>function bweb_wpsrd_capability() {
 return 'edit_post';
}
add_filter('wpsrd_capability', 'bweb_wpsrd_capability');
</code></pre>
<h4>Languages</h4>
The plugin only bears a few sentences, but you can easily translate them through .MO & .PO files. Currently available languages are:
<ul>
<li>English</li>
<li>French</li>
<li>Deutsch – Thanks to <a href="https://profiles.wordpress.org/mallard66" title="mallard66" rel="nofollow ugc">mallard66</a></li>
<li>Dutch – Thanks to <a href="https://profiles.wordpress.org/jondor" title="jondor" rel="nofollow ugc">jondor</a></li>
</ul>
Become a translator and send me your translation! <a href="http://b-website.com/contact" title="Contact" rel="nofollow ugc">Contact-me</a>
<a href="http://b-website.com/category/plugins-en" title="More plugins by b*web" rel="nofollow ugc">CHECK OUT MY OTHER PLUGINS</a>
Please ask for help or report bugs if anything goes wrong. It is the best way to make the community benefit!

Simple Revisions Delete


Installed and activated on WordPress 6.2.2, opened a page in the block editor and clicked Purge. Done.



A really clean implementation of this feature. Very nice work @brikou!



When you get a chance, give it a test run yourself in WordPress 6.3 and update the Tested up to header. This shouldn't be missed out on because of a "Has not been tested with your version of WordPress" message!


Clean and simple

Simple Revisions Delete adds a discreet link within a post submit box to let you purge (delete) its revisions via AJAX. Bulk actions also available.

Daniel Bachhuber

Ipstenu (Mika Epstein)

Danila Vershinin

Kira Schroder

Mike Schroder

techpriester

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.org/" rel="nofollow ugc">NGINX</a>. These systems allow a website to update content and have the visitor’s experience cached without the need for complex plugins storing the files locally and using up a user’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’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 pages 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’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 -> 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>Cache Tags (BETA)</h4>
As of version 5.4.0, Proxy Cache Purge includes an optional Cache Tags / Surrogate Keys purge mode. This feature is marked as BETA and is disabled by default.
When enabled, the plugin:
<ul>
<li>Adds cache-tag headers to WordPress responses (for example, tagging pages by post ID, post type, taxonomy terms, author, and archives).</li>
<li>Uses tag-based purges instead of individual URL purges when content is updated, which can reduce purge traffic and improve consistency on complex sites.</li>
</ul>
Requirements:
<ul>
<li>A proxy cache that supports Cache Tags / Surrogate Keys and advertises this via standard <code>Surrogate-Capability</code> headers (for example, <code>Surrogate-Capability: vhp="Surrogate/1.0 tags/1"</code>).</li>
</ul>
How to enable:
<ul>
<li>Go to Proxy Cache → Settings → Purge Method and check “Use Cache Tags (Surrogate Keys)”. The checkbox is only enabled when your cache tells WordPress it supports tags (or when you explicitly enable it via a define).</li>
<li>
Alternatively, you can force-enable or force-disable detection via <code>wp-config.php</code>:
define( ‘VHP_VARNISH_TAGS’, true ); // Force treat cache as tag-capable 
define( ‘VHP_VARNISH_TAGS’, false ); // Force treat cache as not tag-capable
</li>
</ul>
Because this feature depends on your cache configuration, it is recommended that you test it carefully in staging before enabling it on production.
<h4>Background Purging with WP-Cron</h4>
On busy sites, sending many PURGE requests directly from admin requests can slow things down. When you define <code>DISABLE_WP_CRON</code> as <code>true</code> in <code>wp-config.php</code> (because you are running a real system cron that calls <code>wp-cron.php</code>), Proxy Cache Purge automatically switches to an asynchronous mode:
<ul>
<li>Purge requests (both URL-based and tag-based, when Cache Tags are enabled) are collected into a small per-site queue.</li>
<li>The queue is processed by WP-Cron in the background, keeping your admin and content-editing actions responsive even when many URLs or tags must be invalidated.</li>
</ul>
Object-cache purges (the \”Purge Database Cache\” option) remain synchronous and are not affected by this behaviour. The Proxy Cache settings page and Site Health integration expose basic queue status so you can verify that background purging is healthy; if the queue appears large or very old, check that your system cron is correctly invoking WordPress cron.
Important: Cron Frequency and Cache Freshness
When using background purging, the frequency of your system cron determines how quickly cache invalidations are processed. The longer the interval between cron runs, the longer visitors may see stale content after updates.
For minimal stale content, run your system cron every minute:
<pre><code>* * * * * /usr/bin/php /var/www/html/wp-cron.php
</code></pre>
If you can tolerate slightly longer delays, every 2-5 minutes is also acceptable. However, running cron less frequently (e.g., every 15 minutes) means cache purges may be delayed by that amount after content changes.
Note: Scheduled posts are handled specially. When a scheduled post is published via WP-Cron, the cache is purged synchronously within the same cron run, ensuring immediate cache invalidation without waiting for the next cron execution.
For detailed instructions on setting up a proper Linux-based WordPress cron, see: <a href="https://www.getpagespeed.com/web-apps/wordpress/wordpress-cron-optimization" rel="nofollow ugc">WordPress Cron Optimization</a>.
<h3>WP CLI</h3>
Purge
Purge commands let you empty the cache.
<ul>
<li><code>wp varnish purge</code> – Flush the cache for your front page</li>
<li><code>wp varnish purge [<url>]</code> – 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’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 [<url>]</code></li>
</ul>
Available parameters:
<ul>
<li><code>[--include-headers]</code> — Include headers in debug check output</li>
<li><code>[--include-grep]</code> — 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 [<activate|deactivate|toggle>]</code> – Change development mode state</li>
</ul>
Async purge queue (cron-mode)
When you define <code>DISABLE_WP_CRON</code> as <code>true</code> and run a real system cron for WordPress, Proxy Cache Purge can move heavy purge work into a small background queue that is processed by WP‑Cron.
You can inspect and manage that queue via WP‑CLI:
<ul>
<li><code>wp varnish queue status</code> – show whether cron-mode is active, if a full purge is queued, counts of queued URLs/tags, and the last queue run time.</li>
<li><code>wp varnish queue process</code> – process any items currently in the queue (useful to run after deploys or cache‑sensitive operations).</li>
<li><code>wp varnish queue clear</code> – clear the queue without sending any PURGE requests.</li>
</ul>
These commands do not replace your normal WordPress cron (you still need a cron entry that calls <code>wp cron event run --due-now</code> or hits <code>wp-cron.php</code>), but they give you a simple operational handle when using cron‑mode.

Proxy Cache Purge

Automatically empty proxy cached content when your site is modified.

Simple Revisions Delete vs Proxy Cache Purge