WordPress plugin
Paradarum CDN Purge is the official WordPress plugin. It automatically invalidates the affected CDN routes through the purge API whenever you publish or edit content — so visitors never see a stale page or listing.
⬇ Download the WordPress plugin (wordpress.zip)
Version 1.0.0 · Requires WordPress 5.6+ and PHP 7.4+ · GPL‑2.0‑or‑later
What it purges
When content changes, the plugin doesn't just purge the single URL — it purges every route that listing could appear on. It hooks into:
| Event | WordPress hooks |
|---|---|
| Publishing / updating / unpublishing / trashing a post or page | transition_post_status, pre_post_update |
| A comment being posted or approved | comment_post, transition_comment_status |
| Creating, editing or deleting a term (category, tag, taxonomy) | created_term, edited_term, delete_term |
For a single post it can purge the post URL plus the home page, the relevant category/tag/taxonomy archives, author and date archives, feeds and the sitemap. Each of these is configurable (see Configuration).
Install
- In your WordPress admin, go to Plugins → Add New → Upload Plugin.
- Choose the
wordpress.zipyou downloaded above and click Install Now. - Click Activate.
- Open Settings → Paradarum CDN to configure it.
:::note Folder name
The archive installs into a paradarum-cdn-purge/ plugin folder. If you extract it
manually, upload that folder to wp-content/plugins/.
:::
Configuration
Open Settings → Paradarum CDN and fill in:
| Setting | What to enter |
|---|---|
| API key | An account API key (pdm_…). Create one in the panel — see Manage API keys. Stored encrypted (AES‑256‑CBC) in the database. |
| Property ID | The numeric ID of the property that serves this site (visible in the panel, or from GET /api/property). |
| Auto purge | On by default. Turn off to disable automatic purging and only purge manually / via WP‑CLI. |
| Strategy | hybrid (default), surgical, or broad — how aggressively related routes are purged. |
| Import threshold | Default 30. If a single change would purge more than this many paths, the plugin collapses it into one full‑property purge (set 0 to never collapse). Protects against bulk imports flooding the API. |
| Include toggles | Taxonomies, author archives, date archives, feeds, sitemap — each can be excluded from related‑route purges. |
The API base URL is fixed to https://api.paradarum.com.
:::tip Store the API key in wp-config.php (recommended)
For production, define the key as a constant so it never lives in the database and isn't
editable from the UI:
// wp-config.php
define( 'PARADARUM_API_KEY', 'pdm_your_key_here' );
// Optional: override the API base URL (e.g. staging).
// define( 'PARADARUM_API_URL', 'https://api.paradarum.com' );
When PARADARUM_API_KEY is defined it takes precedence and the key field in the UI is
locked.
:::
WP‑CLI
The plugin registers a paradarum command:
# Purge the entire property cache
wp paradarum purge --all
# Purge a single URL or path
wp paradarum purge --url=https://example.com/blog/
# Purge everything affected by a post
wp paradarum purge --post=42
# Show configuration / connection status
wp paradarum status
How it relates to cache rules
The plugin handles invalidation (purging when content changes). It pairs naturally with the WordPress cache rules, which control what gets cached and for how long. Apply the rules (or the one‑click CMS preset) for caching, then install this plugin so the cache stays fresh automatically.
Troubleshooting
- Nothing is purging: confirm
wp paradarum statusshowsReady: yes(it needs a valid API key and a Property ID greater than 0). 403responses: the property is disabled or suspended — see purge behavior & limits.401responses: the API key is invalid or revoked — generate a new one in Manage API keys.