Verify the QCDR System Plugin and Frontend Runtime Path

QCDR live replacement depends on the package-owned System plugin. The component stores Rules, Tokens, settings, and diagnostics, but the System plugin is what marks Joomla frontend render boundaries and hands the final HTML body to the RuntimeEngine.

If Rules and Tokens look correct in Administrator but nothing changes on eligible frontend HTML, verify this runtime path before rebuilding content.

What the System Plugin Does

The current plugin subscribes to three Joomla events:

  • onAfterDispatch: marks the rendered frontend component buffer so QCDR can identify the component region later.
  • onAfterRenderModule: marks rendered site-module output and its module identity.
  • onAfterRender: builds the current request context, runs the RuntimeEngine, and writes the final processed body back to Joomla.

Those temporary boundary markers are stripped from ordinary visitor output. Authorized Discovery can retain them long enough to prove render boundaries privately.

Verify the Installed Runtime Member

  1. In Joomla Administrator, open System > Manage > Extensions.
  2. Locate the QC Dynamic Replacer System plugin and confirm it is installed and enabled.
  3. Confirm the component and Task plugin belong to the same current QCDR package/version.
  4. If the System plugin files are missing or the package is inconsistent, install the current outer QCDR package over the existing installation rather than uninstalling first.

Confirm the Request Is Eligible

The normal runtime processes only the Joomla site client and HTML output. Administrator output is excluded. Non-HTML formats are excluded, as are the protected com_users login, reset, and remind views. A normal request also needs Rule Live Processing, Token Live Processing, or both enabled.

Preview and Discovery have their own signed private authorization paths and do not prove that ordinary live processing is enabled.

Check Both Live Processing Switches

Rule Live Processing and Token Live Processing are independent. If both are off, ordinary QCDR runtime changes stop. If only Token processing is off, direct-value Rules can still run, but standalone Tokens and Token-dependent Rules remain unapplied. If only Rule processing is off, eligible standalone Tokens can still resolve.

Diagnose a Missing Runtime Path

  • If nothing QCDR-related changes on eligible frontend HTML, check the System plugin and Live Processing first.
  • If direct Rules work but standalone Tokens do not, check Token Live Processing and Token state/targeting.
  • If only one page fails, check that page's targeting, content type, response format, caching, and protected regions instead of reinstalling immediately.
  • Use the QCDR Status tab for installation/version context, then inspect Joomla's Extension Manager when a package member appears missing.

Community Discussion

Want to compare workflows, share practical tips, or discuss how you use this QCDR feature? Visit the QC Dynamic Replacer Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.