PrestaShop module
Paradarum CDN Purge is the official PrestaShop module. It automatically invalidates the affected CDN routes through the purge API whenever your shop content changes — products, categories, CMS pages, manufacturers and suppliers.
⬇ Download the PrestaShop module (prestashop.zip)
Version 1.0.0 · PrestaShop 1.7.0.0 → 8.x · Author: Paradarum
What it purges
The module hooks into PrestaShop's object lifecycle and purges the affected routes when these entities are added, updated or deleted:
| Entity | Hooks |
|---|---|
| Product | actionObjectProductAddAfter / UpdateAfter / DeleteAfter |
| Category | actionObjectCategoryAddAfter / UpdateAfter / DeleteAfter |
| CMS page | actionObjectCmsAddAfter / UpdateAfter / DeleteAfter |
| Manufacturer | actionObjectManufacturerAddAfter / UpdateAfter / DeleteAfter |
| Supplier | actionObjectSupplierAddAfter / UpdateAfter / DeleteAfter |
A product change, for example, can purge the product page plus its category pages and the home page, depending on your include settings below.
Install
- In your PrestaShop back office, go to Modules → Module Manager.
- Click Upload a module and choose the
prestashop.zipyou downloaded above. - After it installs, click Configure.
The archive contains a paradarumcdn/ module folder. If you upload by FTP instead, place
that folder in your shop's modules/ directory and install it from the Module Manager.
Configuration
On the module's Configure screen, 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 shop configuration. |
| Property ID | The numeric ID of the property that serves this shop (visible in the panel when you open the property). |
| Auto purge | On by default. Turn off to disable automatic purging. |
| Strategy | hybrid (default), surgical, or broad — how aggressively related routes are purged. |
| Threshold | Default 30. If a single change would purge more than this many paths, the module collapses it into one full‑property purge. |
| Include toggles | Category, CMS, manufacturer, supplier and sitemap routes — each can be excluded from related‑route purges. |
The API base URL is fixed to https://api.paradarum.com.
For production you can define the key as a constant (for example in config/defines_custom.inc.php)
so it never lives in the database and isn't editable from the UI:
define('PARADARUM_API_KEY', 'pdm_your_key_here');
// Optional: override the API base URL.
// define('PARADARUM_API_URL', 'https://api.paradarum.com');
When PARADARUM_API_KEY is defined it takes precedence and the key field is locked.
How it relates to cache rules
The module handles invalidation (purging when content changes). It pairs with the PrestaShop 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 module so the cache stays fresh automatically.
PrestaShop randomizes the admin folder name for security. The cache rules
assume a default /admin path — adjust the never‑cache rule to match your real admin folder.
Troubleshooting
- Nothing is purging: confirm the module shows it is ready (it needs a valid API key and a Property ID greater than 0), and that Auto purge is on.
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.