Help4 Net
Joomla extension tutorial

Install Help4 CDN for Joomla

The package installs one administrator component, one shared library, and one content plugin so Joomla can synchronize its Help4 service, clear site-scoped cache, request scans, and invalidate public content after changes.

Initial release: install on staging first, take a Joomla backup, and confirm the site is on Joomla 5.4 or Joomla 6 with PHP 8.1 or newer before production use.

What the package installs

PackageInstalls the three version-matched Joomla extensions together.
LibraryNormalizes paths and sends site-scoped Help4 API requests.
ComponentProvides connection, cache, scan, WAF, bot, header, and access controls.
Content pluginClears public cache after supported content changes without blocking a save on API failure.

Install and enable

  1. Back up Joomla.
    Take a current file and database backup and confirm that it can be restored.
  2. Download the package ZIP.
    Keep help4-cdn-joomla-0.1.0.zip intact; do not install one constituent ZIP separately.
  3. Open the extension installer.
    In Joomla administrator, go to System, Install, then Extensions.
  4. Upload and install.
    Choose the Help4 package ZIP and wait for Joomla to confirm the package, library, component, and plugin installation.
  5. Enable automatic invalidation.
    Go to System, Manage, Plugins, find Content - Help4 CDN automatic invalidation, and enable it.
  6. Open Help4 CDN.
    Go to Components, Help4 CDN. The dashboard requires permission to manage the component.

Connect the site

  1. Enter the Help4 API key and secret.
    Use the tenant-scoped pair from the private service handoff. Use the legacy token only when Help4 operations specifically requires it.
  2. Save connection settings.
    Credential fields clear after saving and show only a stored-value placeholder. Leaving them blank preserves the stored values.
  3. Select Synchronize site.
    The extension discovers or registers the production hostname, captures its Help4 site ID and plan, then sends a heartbeat.
  4. Review the effective plan.
    Controls outside the active entitlement may be rejected or remain ineffective even if the local form can describe them.
  5. Start with conservative policy.
    Keep static-only delivery, origin cache policy, and managed bot protection until public and administrator routes are verified.
Credentials are never printed back into the administrator page. They remain in Joomla component parameters and should still be protected by normal server, database, and administrator-access controls.

Verify the installation

  • The dashboard shows a Help4 site ID.
  • The plan and license fields are populated.
  • The content plugin is enabled.
  • A selected-path cache clear is accepted.
  • A public article still renders correctly.
  • Joomla administrator and login routes remain private.
  • A saved article causes a queued or accepted invalidation.
  • Public headers identify the expected Help4 POP and policy.
curl -sSI https://example.com/
curl -sS https://example.com/article-alias | openssl dgst -sha256
Next: use the Joomla cache tutorial before enabling broader proxy or WAF settings.

Update or remove

Install a newer package over the existing package when Help4 publishes an update. Do not replace only one constituent extension. To remove it, use Joomla's Extensions list and uninstall the Help4 CDN package so its packaged parts stay version-aligned.

The update feed is published at /downloads/help4-cdn-joomla-update.xml. Verify the package checksum against the CMS checksum manifest when downloading outside Joomla.