Use Explain This Output from a QCDR Page Scan

Move scan result into the normal inspector/evidence/fingerprint workflow, evaluate likely origins, and avoid treating advisory evidence as automatic target authority.

This guide follows the accepted QC Dynamic Replacer 1.1.05 implementation and applies to Max / All Access + Run Discovery ACL. Where older manuals or walkthrough wording differs from the current source or the accepted keyless-entitlement behavior, the current implementation takes precedence.

Before You Begin

Discovery is private and same-origin; open it from the authorized Administrator workflow.
Treat evidence/confidence as guidance, not as permission for automatic retargeting.
Use bounded scans and close/restart sessions when authorization expires.

Step-by-Step Workflow

Confirm Effective Max/All Access and the Run Discovery permission.
Open Discovery from QCDR Administrator and enter a safe same-site frontend URL.
Launch a fresh private session; do not reuse an expired authorization.
Select output, search for a phrase, or run the bounded analysis tool relevant to the question.
Review evidence, confidence, render context, Rule effects, and any captured fingerprint.
If appropriate, prepare a Draft Rule from the finding; review its scope and replacement before saving.
Exit Discovery and verify the eventual Rule independently before enabling it for ordinary visitors.

Discovery Tool Reference

Tool	Purpose
Click It, Change It	Select rendered output privately and inspect evidence before creating a Draft Rule.
Page Scan	Bounded inventory of notable text/headings, links/buttons, media, forms, Token regions, component/module markers, and Rule effects.
Explain This Output	Move a Page Scan result into the standard evidence/fingerprint inspector.
Site Impact Scan	Check the current page, published menu routes, and supplied same-site URLs; current limit is 40 de-duplicated pages.
Dynamic DOM Watch	Observe late browser-side DOM mutation for up to 60 seconds or 600 mutation records; timing is evidence, not JavaScript call-stack attribution.

Move scan result into the normal inspector/evidence/fingerprint workflow

QCDR targeting narrows runtime eligibility before replacement occurs. Basic can scope by frontend pages/menu items and URL/path patterns. Pro adds component or supported site-module boundaries and audience targeting for guests, authenticated users, or selected Joomla groups. Targeting is evaluated against the actual request context, so a Rule can be correctly configured yet inactive on a page that does not match every selected gate. Personalized output also requires cache planning so a full-page or CDN cache does not serve one audience variant to another visitor.

For Use Explain This Output from a QCDR Page Scan, evaluate this against the exact frontend request that matters. A saved QCDR item can be valid in Administrator yet remain inactive because a different eligibility gate, dependency, permission, cache layer, or runtime safety boundary correctly prevents transformation. Keeping those concerns separate makes both testing and later support much easier.

Evaluate likely origins

And avoid treating advisory evidence as automatic target authority

How This Fits into QCDR

Discovery is intentionally non-mutating until you deliberately carry a finding into a Draft Rule and review/save it.

The safest operating pattern is to keep configuration narrow, use QCDR’s private diagnostics before broad activation when your tier permits them, and preserve Joomla Administrator as the recovery surface. Because QCDR changes the rendered response rather than source files, a correctly disabled or bypassed runtime path should expose the underlying Joomla output again without requiring a source-file rollback.

Verify the Result

Reload the real frontend request instead of relying only on the saved Administrator form.
Check Joomla/CDN cache effects if the result is request-specific.

Common Mistakes to Avoid

Changing several gates at once during troubleshooting, which makes the actual cause difficult to identify.
Testing only while signed in as Super User when ordinary users/guests are the intended audience.
Skipping a recovery plan before enabling a site-wide HTML, JavaScript, protected-area, or PHP-backed change.

Troubleshooting

If nothing changes, confirm the package-owned System plugin is enabled, the relevant Live Processing switch is on, and the item is eligible for the current Effective tier.
If targeting appears wrong, inspect page/menu/URL, extension, audience, schedule, IP, technical conditions, and protected-region behavior as separate gates.
If a Token-backed Rule preserves the original match, troubleshoot the Token dependency/readiness before changing the Find value.
If behavior differs between browsers/users, clear or bypass relevant Joomla/full-page/CDN caches and compare request context.
If private Preview/Discovery fails, start a fresh authorized same-site session and confirm the Joomla ACL action as well as the product tier.

Operational Best Practice

Make runtime changes deliberately: use a narrow scope first, keep broad Rules Draft or Disabled until tested, preserve the independent Rule/Token emergency switches, and record the QCDR version plus the exact Rule/Token and affected URL when handing a problem to another administrator. For high-impact HTML, protected-region, JavaScript, dynamic-data, or PHP work, test representative anonymous and authenticated requests and review caching before expanding scope.

Community Discussion

Want to compare workflows, share practical examples, or discuss how other administrators use this QCDR feature? Visit the QC Dynamic Replacer Community. For private support, bug reports, account-specific entitlement problems, or feature requests, use the QuantaCade support system.