QC Dynamic Replacer Glossary and Current Terminology
Use this glossary when reading QCDR 1.1.05 documentation, Status messages, Rule Health results, and support guidance. These definitions describe the current rendered-output product model rather than older source-editing or license-key terminology.
Core Runtime Terms
- Rule
- A saved instruction that finds eligible rendered frontend content and replaces, removes, inserts, wraps, or changes it when all of the Rule's runtime gates pass.
- Token
- Reusable QCDR output referenced as
{token.name}. The same Token can appear directly in eligible frontend output or be selected as a Rule replacement source. - Rule Live Processing
- The Rules-tab switch controlling ordinary live Rule execution.
- Token Live Processing
- The Tokens-tab switch controlling ordinary standalone Token resolution and Token-dependent Rule replacement. It is independent from Rule Live Processing.
- Rendered output
- The frontend HTML Joomla produced for the current request. QCDR transforms eligible rendered output; it does not patch Joomla, extension, or template source files.
- Protected region
- A script-, style-, code-like, form, comment, or other sensitive output region that QCDR avoids by default. Max-level Rules can deliberately opt into protected-area Rule processing where supported.
Entitlement Terms
- Authorized Domain
- The current keyless QuantaCade entitlement identity for the Joomla site's normalized hostname.
- Base tier
- The underlying QCDR product entitlement, such as Basic, Pro, or Max. All Access supplies Max-level QCDR feature rank.
- Effective tier
- The feature level QCDR is allowed to enforce now after entitlement status, All Access/preview elevation, expiration, communication grace, and required task integrity are considered.
- 30-Day Max Preview
- The one-time server-authoritative Max feature preview. In 1.1.05 it begins only when an authorized administrator explicitly starts it.
- Entitlement Revalidation
- The canonical QCDR Scheduled Task that must remain uniquely published and run at least hourly for Effective access above Basic.
- Legacy License Key
- Compatibility state left from older releases. Current normal paid activation is Authorized-Domain based; Clear Saved Key removes obsolete local key/update state without deleting QCDR content.
Testing and Discovery Terms
- Preview
- A private, signed frontend test of one exact saved Rule on a real same-site request. It can test Draft or Disabled Rules without making them live.
- Rule Health
- The diagnostic report attached to private Preview that explains state, targeting, audience, schedule, IP, conditions, Token readiness, matches, protected regions, fingerprints, and final live eligibility.
- Discovery
- QCDR's private frontend analysis environment for selecting visible output, scanning a page, explaining evidence, checking bounded site impact, and watching late DOM mutation.
- Target Fingerprint
- Versioned advisory evidence captured from Discovery to help Rule Health detect target drift. A fingerprint never authorizes QCDR to silently retarget a Rule.
- Dynamic DOM Watch
- A bounded Discovery tool that records browser-side DOM changes after the watch begins. It proves mutation timing, not which JavaScript file caused the change.
Token and Data Terms
- Joomla dynamic-data Token
- A Max-level Token that reads current Joomla/request, article, custom-field, module, menu, or user data at request time while respecting current publication and visitor-access rules.
- PHP Token
- A Max-level Token containing trusted server-side PHP. Authoring requires the dedicated Manage PHP Tokens permission. PHP execution is not sandboxed.
- Unresolved Token
- An internal safe-failure condition where QCDR deliberately preserves the authored placeholder or the Rule's original matched content instead of replacing it with misleading blank output.
Administration and Recovery Terms
- Dynamic Replacer Workspace
- The optional frontend readiness dashboard showing stored/enabled Rule and Token counts. Rule and Token editing remains an Administrator workflow.
- Emergency bypass
qcdr_bypass=1on a frontend request by an authorized Super User. It skips QCDR for that request without changing saved configuration.- Stop Processing
- A paid Rule option that stops later Rules only after the current Rule actually performs at least one replacement. Standalone Token resolution can still follow.
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.