Choose What a QCDR Rule Should Find

A QCDR Rule searches the rendered frontend output for the value entered in Find this. The What kind of content? choice describes the kind of rendered content you are targeting; it does not switch QCDR into a source-file editor.

Current Find Types

QCDR 1.1.05 offers these current choices:

  • Anything / detect automatically — a practical default when no more specific type is needed.
  • Text — visible text or other plain-text output.
  • HTML — rendered tags/markup.
  • CSS — CSS text present in eligible rendered output.
  • JavaScript — JavaScript text present in eligible rendered output.
  • PHP source — PHP-like/source text present in rendered output; this does not make QCDR edit a PHP file.
  • URL or image/media reference — rendered URLs and media references.

Enter a Find Value That Can Be Verified

  1. Create or edit a Rule.
  2. Under What do you want to find?, choose the content type.
  3. Paste or type the exact target into Find this.
  4. Use a narrow page/menu/URL scope while proving the match.
  5. Under Matching behavior, choose Exact phrase / whole term or Partial substring, decide whether text case matters, and set the occurrence behavior.

The content type and the match method solve different problems. Content type describes what you are targeting; Exact/Partial, case sensitivity, occurrence selection, and Maximum replacements per page control how matching is performed.

Retired Find Types

Older QCDR data may contain JSON, XML, or INI search classifications. Those choices are retired in the current editor and cannot be selected for a new Rule. QCDR can preserve legacy values in an existing record so upgrading does not silently destroy historical configuration, but they should not be documented as current Rule-building options.

Prefer a Stable Target

Choose a find value that is distinctive enough to avoid unrelated matches but stable enough to survive ordinary Joomla/template changes. If a value appears many times, use page targeting plus Occurrences or Maximum replacements per page instead of assuming the first broad match is safe.

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.