What QC Dynamic Replacer Does and How Runtime Replacement Works

QC Dynamic Replacer (QCDR) changes eligible rendered frontend HTML as Joomla builds a page. It is designed for controlled output transformation: Rules can find rendered content and replace, remove, insert, wrap, or alter it, while reusable Tokens can supply shared content directly or act as Rule replacement sources.

QCDR Works on the Rendered Response

The package-owned System plugin participates in Joomla's frontend render cycle. It marks rendered component and module regions, then processes the final HTML response before Joomla sends it to the visitor. QCDR therefore works with the page Joomla produced for that request; it does not open and rewrite PHP, template, extension, or article source files.

This distinction matters during troubleshooting. Disabling the applicable QCDR processing path exposes the underlying Joomla output again because the original source was not edited by the runtime transformation.

Rules and Tokens Have Independent Live Processing

The Rules tab controls normal Rule Live Processing. The Tokens tab has its own Token Live Processing switch. Turning one off does not automatically disable the other. Turning both off stops ordinary QCDR transformations while leaving saved Rules and Tokens in place.

During a normal request, eligible Rules run in their saved processing order. A Rule can use a direct replacement or a qualifying Token. After Rule processing, QCDR can also resolve enabled standalone {token.name} placeholders that were placed directly in eligible frontend output.

Each Request Is Evaluated in Context

A saved Rule or Token does not necessarily run on every page. QCDR can evaluate page/menu/URL targeting and, when the current Effective tier permits them, extension, audience, schedule, IP, technical-condition, and protected-area controls. Rule ordering, occurrence limits, per-rule limits, and the global replacement limit further constrain what can change.

QCDR processes normal Joomla site HTML only. Administrator output is never a runtime target. Non-HTML responses and Joomla login, password-reset, and username-reminder views are excluded from normal processing.

Safe Failure Preserves Joomla Output

If the runtime engine encounters an unexpected processing exception, QCDR logs a bounded warning and returns the original rendered output rather than publishing a partially transformed response. It also skips processing when the configured response-size limit is exceeded or when an authorized emergency bypass is active.

Token-backed Rules are similarly conservative: if a required Token is unavailable or not eligible for the current request, QCDR preserves the administrator-authored match instead of silently replacing it with an empty value.

Private Preview and Discovery Are Separate Diagnostic Paths

Eligible tiers and Joomla permissions can use private Preview/Rule Health or Discovery on a real frontend request. Those diagnostic requests are separately authorized and sent with no-store/noindex protections. They do not require you to enable a broad Rule for ordinary visitors just to see what it would do.

What QCDR Does Not Do

QCDR 1.1.05 is a rendered-output tool. It does not provide a current workflow for permanently modifying Joomla source files, and ordinary runtime replacement does not rewrite stored Joomla article text, template files, or extension code. If you need a permanent source change, make that change in the system that owns the source rather than treating a QCDR runtime Rule as a file editor.

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.