Skip to main content

CDN modules for CMS platforms

Modules rewrite public image URLs to your site's CDN URL. Browsers load images from Zorka CDN while original files stay on your hosting. No nginx, Apache or .htaccess access is required.

Choose a module​

CMSTested versionGuide
WordPress + WooCommerceWordPress 7.1.3, WooCommerce 11.2.1WordPress
OpenCart 33.0.4.1OpenCart
OpenCart 44.1.0.4OpenCart
ocStore 33.0.4.1ocStore
MODX Revolution 2 / 32.8.9-pl / 3.2.4-plMODX
Joomla 5.4 / 6.x5.4.9 / 6.1.4Joomla
1C-BitrixSeparate moduleBitrix

The new modules start at 0.1.0 (WordPress: 0.1.1). WordPress/OpenCart 3/ocStore 3 modules require PHP 7.4 or later. OpenCart 4 requires PHP 8 and a version compatible with the CMS itself. Tests do not establish compatibility with every older release, theme or extension.

Before installation​

  1. Connect your site's CDN source. Original images must be available over HTTPS without cookies or authentication.
  2. In your account, open the license or subscription and copy its CDN URL. The URL becomes usable after source setup.
  3. Use the entire issued URL, including /s/site_id when present. It is not a license key. A shared domain such as https://cdn.zorka.cloud does not automatically identify your site.
  4. Append a real image path to the CDN URL and test it in a browser before enabling rewriting.

Modules do not register sources automatically or upload files to the CDN. Contact support in your account if the source has not been connected yet.

What changes​

Supported inputs include JPEG, PNG, WebP, AVIF, GIF and BMP, responsive srcset, common lazy-loading attributes, picture, video posters and inline CSS url(). A URL may keep its .jpg extension while the response has Content-Type: image/avif or image/webp: the CDN selects a format using the browser's Accept header.

Original files and content records remain unchanged. Include only public folders and exclude private attachments, paid downloads and personal documents. Path filtering does not replace access control.

SVG, ICO, external domains and common signed URLs remain unchanged. External CSS, JavaScript/JSON strings, headless APIs and custom dynamic galleries need separate integration. There is no automatic origin fallback when the CDN is unavailable.

Verify or disable​

Check pages while logged out: the new modules bypass authenticated users. Inspect HTML src/srcset and image requests in Network for successful responses and correct Content-Type. When exposed, check CDN Vary: Accept and X-Image-Cache headers.

Clear all HTML page caches after configuration changes, disabling or removal. Caches served without PHP may retain old URLs. To roll back, disable the module and clear caches so the CMS generates original URLs again.

Archives and the SHA-256 manifest are linked from the guides. Reverse proxy configuration is a separate integration method.