When you publish, update, unpublish or trash a post or page — or edit a term, or a comment is approved — this plugin invalidates the affected CDN routes through the Paradarum API, using your account API key.
It does not just purge the single post: it also purges the home page, the relevant category/tag/taxonomy archives, author and date archives, feeds and sitemaps, so visitors never see a stale listing.
starts_with) so their pagination (/page/2/, …) is invalidated too.All routes affected during a request are collected, de-duplicated and sent to the API in a single batch call on shutdown, so saving in the editor is never slowed down by many HTTP requests. If a single save or import touches more paths than the configurable threshold, the plugin collapses everything into one full-site purge instead.
This plugin requires a Paradarum CDN account: your site must be configured as a property on the Paradarum CDN, and you need an API key generated from the Paradarum console. Without an account the plugin has nothing to purge.
This plugin connects to the Paradarum CDN API (https://api.paradarum.com), the service that hosts and caches your site’s content. This connection is the core purpose of the plugin and cannot be disabled.
What is sent, and when:
X-API-Key request header) — on every API call, to authenticate./my-post/ or /category/news/).No visitor data, personal data, analytics or telemetry is ever transmitted. Requests are only sent after you have configured your own API key.
This service is provided by Paradarum: terms of service — privacy policy.
wp paradarum status
wp paradarum purge --all
wp paradarum purge --url=/blog/
wp paradarum purge --post=42<h3>Developer hooks</h3>
Trigger a purge from your own code:
do_action( 'paradarum_purge', array( home_url( '/landing/' ) ) );
do_action( 'paradarum_purge', 'all' );
Filter the final purge items before they are sent:
add_filter( 'paradarum_cdn_purge_items', function ( $items, $trigger ) {
return $items;
}, 10, 2 );