Current vs Retired QCDR Features: Avoiding Obsolete Instructions

QC Dynamic Replacer has preserved some older database values and internal code so upgraded sites remain safe, but those artifacts are not all current customer workflows. Use this guide to distinguish QCDR 1.1.05 behavior from obsolete instructions.

Current Administrator Navigation

The current customer-facing QCDR Administrator interface has exactly seven primary tabs:

  • About
  • Support
  • Status
  • Settings
  • Rules
  • Tokens
  • Discovery

Older references to Email Templates, Frontend Design, Frontend Text, Observe, Playground, Code & Assets, or similar internal/legacy surfaces should not be followed as normal 1.1.05 navigation merely because implementation remnants still exist in the codebase.

Current Runtime Model: Rendered Frontend Output

Current Rules operate on eligible rendered Joomla frontend output. The Rule editor stores rendered-output matching and explicitly states that QCDR never edits Joomla source files.

A current Rule can classify its find content as Anything/automatic, Text, HTML, CSS, JavaScript, PHP source, or URL/media reference. PHP source in this list means PHP-like text that actually appears in rendered output; it does not open or patch .php files.

Retired Source-File Rules

Older records can retain a legacy source_files location for preservation. In the current editor those Rules are identified as legacy, remain stored, and cannot run as the old source-file workflow. Recreate any still-needed behavior as a rendered-output Rule instead of looking for a file patcher.

Retired Count Only and Structured Find Types

Count Only is not a current action for new Rules. An upgraded legacy Count Only Rule can remain stored, but current saves preserve it only as retired compatibility state rather than offering it as a new workflow.

JSON, XML, and INI are likewise retired Rule search-content types. The current editor can preserve an existing legacy value but does not offer these types for new configuration.

Current and Retired Token Output Types

Current Token output types are Plain text, HTML/formatted content, Image/media, Link/button, Joomla content/dynamic data, CSS, JavaScript, PHP code, and URL link, subject to their plan and permission gates.

Older Structured Data/JSON, XML, INI/language-value, and HTML-attribute output types are labeled as retired compatibility values. Do not write new documentation that instructs customers to create them as current Token workflows.

Current Entitlement vs. Old License-Key Instructions

QCDR 1.1.05 resolves normal paid access from Authorized Domains. A saved legacy key can still appear on an upgraded site, but it is compatibility/history state rather than the current activation method. Clear Saved Key is a cleanup/migration action, not a replacement for authorizing the domain.

Current update discovery is also keyless; 1.1.05 removed the obsolete package dlid dependency.

Current Max Preview vs. Older Preview Wording

Instructions describing a 3-day preview, an automatically consumed preview, or preview activation merely by opening QCDR are obsolete. The current one-time 30-Day Max Preview starts only when an authorized administrator explicitly chooses Start 30-Day Max Preview. Installation, ordinary Administrator navigation, Refresh Entitlement, Scheduled Tasks, and frontend traffic do not consume an unused preview.

Current Upgrade Practice

Upgrade by installing the current outer QCDR package over the existing installation. Do not uninstall first as a routine update step. The current package preserves Rules, Tokens, settings, paid configuration, and preview history while its installer repairs package/runtime/task state where possible.

How to Judge an Older Instruction

If an older walkthrough conflicts with the 1.1.05 UI or source, follow the current implementation. In particular, reject instructions that require hidden tabs, direct source-file editing, Count Only, JSON/XML/INI creation, customer-entered activation keys, automatic/3-day previews, or uninstall-before-upgrade. Preserve old records when QCDR does so, but do not present preserved compatibility data as a current workflow.

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.