Rendered Output vs Source Files in QC Dynamic Replacer

QC Dynamic Replacer 1.1.05 is a rendered-output system. It transforms eligible Joomla frontend HTML as the response is being produced; it does not open and rewrite Joomla PHP, template, CSS, JavaScript, or other source files on disk.

Where Current Rules Operate

The QCDR System plugin receives eligible frontend rendered output and passes it through the runtime engine. Current Rule records are created for rendered_output, and normal runtime loading excludes source-file Rules.

This means a Rule can change what a visitor receives without permanently editing the article, template, extension file, or other source that originally produced that output.

“PHP source” Does Not Mean PHP File Editing

The Rule editor includes PHP source as a current What kind of content? classification. That label describes PHP-like/source text if it appears in eligible rendered output. It does not grant filesystem access and does not make QCDR modify a .php file.

The same rendered-output boundary applies to the CSS and JavaScript find classifications: QCDR is matching content in an eligible response, not acting as a source-code deployment tool.

What Happened to Legacy Source-File Rules

Older QCDR versions could leave source-file-related configuration in the database. Version 1.1.05 preserves a legacy source-file Rule rather than destroying it during an edit, but the editor identifies it as retired and normal runtime processing will not run it.

If the old behavior is still needed conceptually, recreate the requirement as a rendered-output Rule where possible. Do not expect an old source-file Rule to continue changing files after upgrade.

Why This Boundary Matters

  • Disabling a Rule stops the runtime transformation without requiring a source-file rollback.
  • Updating Joomla or an extension is less likely to overwrite a QCDR change because QCDR is not patching that extension's files.
  • You still need to retest Rules after frontend markup changes because the rendered value being searched for may change.
  • QCDR should not be used as a substitute for proper source control when you actually need to alter PHP, template, CSS, or JavaScript files.

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.