Skip to main content

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. Since v1.1.0 it can also serve your static assets through the CDN without any DNS change.

⬇ Download the WordPress plugin (wordpress.zip)

Version 1.1.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:

EventWordPress hooks
Publishing / updating / unpublishing / trashing a post or pagetransition_post_status, pre_post_update
A comment being posted or approvedcomment_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​

  1. In your WordPress admin, go to Plugins → Add New → Upload Plugin.
  2. Choose the wordpress.zip you downloaded above and click Install Now.
  3. Click Activate.
  4. Open Settings → Paradarum CDN to configure it.
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:

SettingWhat to enter
API keyAn account API key (pdm_…). Create one in the panel — see Manage API keys. Stored encrypted (AES‑256‑CBC) in the database.
Property IDThe numeric ID of the property that serves this site (visible in the panel when you open the property).
Auto purgeOn by default. Turn off to disable automatic purging and only purge manually / via WP‑CLI.
Strategyhybrid (default), surgical, or broad — how aggressively related routes are purged.
Import thresholdDefault 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 togglesTaxonomies, author archives, date archives, feeds, sitemap — each can be excluded from related‑route purges.
Serve static assets through CDNOff by default. Rewrites wp-content/wp-includes asset URLs to your CDN hostname — see below. (v1.1.0+)
CDN hostnameThe hostname assets are served from when the mode above is on — your property's your-property.prdrm.net system hostname, or a custom hostname that is Active on the property. (v1.1.0+)

The API base URL is fixed to https://api.paradarum.com.

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.

Serve static assets through CDN​

Available since v1.1.0.

This mode offloads your static files to Paradarum without moving the whole site behind the CDN. When enabled, the plugin rewrites the URLs of assets under wp-content/ and wp-includes/ in your rendered pages so browsers fetch them from your CDN hostname instead of your web host:

Before:  https://www.example.com/wp-content/themes/mytheme/style.css
After:   https://my-site.prdrm.net/wp-content/themes/mytheme/style.css

The CDN fetches each asset once from your origin (your WordPress site), caches it at the edge, and serves it to visitors from the nearest PoP. Your HTML pages keep being served directly by your host.

Why it is useful​

  • No DNS changes required. Because assets are served from the property's *.prdrm.net system hostname, this works the moment your property exists — you never have to touch your domain's DNS or connect a domain at all. It is the fastest way to get real CDN benefit on a site you cannot (or don't want to) repoint yet.
  • Immediate wins. Themes, plugin assets, uploaded images and core scripts — typically the bulk of page weight — get edge caching, compression and the property's static-assets cache rule.

Enable it​

  1. Make sure the Paradarum property's origin points at this WordPress site, so the CDN can fetch the assets. (If you created the property with the wizard, it already does.)
  2. In Settings → Paradarum CDN, turn on Serve static assets through CDN.
  3. The CDN hostname field defaults to your property's system hostname (your-property.prdrm.net). If your domain is already connected to the property you can use a custom hostname instead — it must be Active (green) on the property.
  4. Save. Reload a page on your site and check the source: asset URLs under wp-content/wp-includes now point at the CDN hostname.

Limits​

Only wp-content and wp-includes are rewritten

The mode rewrites asset URLs under wp-content/ (themes, plugins, uploads) and wp-includes/ (core scripts and styles) only. HTML documents, wp-admin, REST/AJAX endpoints, and any URL outside those two paths are untouched and keep being served by your host. To put the whole site behind the CDN, connect your domain instead — see Connect your domain.

Purging keeps working as before: when the plugin purges a route, asset variants cached under the CDN hostname are covered by the same property purge.

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 status shows Ready: yes (it needs a valid API key and a Property ID greater than 0).
  • 403 responses: the property is disabled or suspended — see purge behavior & limits.
  • 401 responses: the API key is invalid or revoked — generate a new one in Manage API keys.