WordPress plugin intelligence profile

Paradarum CDN Purge

Automatically purges the Paradarum CDN cache for the routes affected whenever you publish or modify content.

WP PlugIndex snapshot

Current directory snapshot

Tested up to WordPress 7.0
Current version1.0.0
WordPress coverageTested up to WordPress 7.0
Minimum stackWP 5.6 · PHP 7.4
Directory statusactive
Last directory update20 Jul 20263mo ago
Active installationsNewAdoption metric — not a quality score
WordPress.org ratingNo WordPress.org ratings yet
Official packageDirect from WordPress.org

Repository metrics are context, not quality scores. Active installations measure adoption and can strongly reflect a plugin’s age and historical popularity. Ratings, recent updates and “Tested up to” metadata also do not guarantee modern code, error-free operation, security, feature completeness or suitability for a particular site. Why active installs don’t tell the whole story →

WP PlugIndex currently records Paradarum CDN Purge version 1.0.0 as active, updated 3mo ago and tested up to WordPress 7.0.

Overview

About this plugin

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.

How it decides what to purge

  • Hybrid (recommended): the post and the home are purged by exact path; archives and listings are purged by path prefix ( starts_with ) so their pagination ( /page/2/, …) is invalidated too.
  • Surgical: only exact URLs are purged (archive pagination may stay cached).
  • Broad: any change flushes the whole site cache.

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.

Requirements

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.

External services

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:

  • Your account API key (as the X-API-Key request header) — on every API call, to authenticate.
  • When you click Check & detect in the settings: a request to list the properties (sites) of your account, so the plugin can match this site’s domain.
  • When content changes (publish/update/trash of posts or pages, term edits, comment approval) and when you use the manual purge tools or WP-CLI commands: the property id and the list of URL paths to invalidate (for example /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-CLI

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 );

WordPress.org metadata

Plugin tags

Topics listed for this plugin in the WordPress.org directory.

  • cache
  • cdn
  • performance
  • purge
Compatibility & maintenance

Compatibility & maintenance

Tested up to WordPress 7.0

Not yet marked as tested with WordPress 7.1. WordPress.org currently lists Tested up to 7.0.

Current WordPress releaseWordPress 7.1
WordPress.org Tested up to7.0
Minimum requirementsWordPress 5.6 · PHP 7.4
Update activity20 Jul 20263mo ago

“Tested up to” is directory metadata supplied by the plugin author. WP PlugIndex does not turn an older declaration into a claim that the plugin is incompatible.

Changes recorded by WP PlugIndex

Recent tracked changes

No tracked version or compatibility changes have been recorded by WP PlugIndex yet.

Tracking & source

WP PlugIndex tracks public WordPress.org directory metadata and records selected version, compatibility and availability changes as they are detected.

Plugin watchlist

Watch this plugin

Sign in to your WP PlugIndex account or create a free account. Free accounts can watch up to 5 plugins and see what changed.

Watch limit

Watchlist limit reached

You have reached your current active watch limit.