What to Include in a QC Dynamic Replacer Support Request

A useful QCDR support request should let QuantaCade reproduce the exact problem without exposing secrets. Include the affected frontend request, the relevant Rule/Token state and targeting, current product/entitlement health, and the evidence you already collected.

Describe the Exact Problem

  • The affected frontend URL or a safe equivalent that reproduces it.
  • What you expected QCDR to change and what actually happened.
  • The Rule or Token name, state, and whether Rule/Token Live Processing was enabled.
  • Whether the problem affects everyone or only a particular login state, Joomla group, IP/network, time window, menu item, component/module, or query condition.
  • Clear reproduction steps from a fresh request.

Include the Support Information Card

Open QC Dynamic Replacer → Support. The current Support Information card provides:

  • Product, Version, Product code, and Domain;
  • masked Saved key status, current Status, and Effective tier;
  • Installation UUID;
  • Joomla version, PHP version, and PHP SAPI;
  • Server software and sanitized server hostname; and
  • open_basedir status/value.

Copy these displayed values instead of reconstructing environment details from memory.

Add the Relevant Diagnostic Evidence

For entitlement problems, include Base/Effective tier, Verification, Last checked, and the Entitlement Automation Integrity result including last exit/next execution when relevant.

For Rule problems, include the Rule Health results or a screenshot of the failing gate. For Preview or Discovery problems, include the exact message and whether the private session could launch. For update problems, include Installed/Available version and Update site state.

Screenshots That Help

Useful screenshots show the rendered frontend result, the relevant QCDR editor section, Status/health card, or Rule Health result. Crop unrelated personal/customer information where possible while leaving labels and error text visible.

Do Not Send Secrets

  • Do not paste passwords, API secrets, authentication headers, cookies, or private session URLs into public community posts.
  • Do not publish PHP Token code containing credentials or customer secrets.
  • Do not expose a full legacy license key. QCDR's Support Information card masks saved-key state for a reason.
  • Do not post sensitive customer/user records merely to demonstrate a Joomla-data Token.

Finish with What You Already Tried

List the specific checks already completed—such as System plugin enabled, cache purged, Live Processing on, Rule Health gate, entitlement refresh, task repair, or install-over-existing repair. That keeps support from asking you to repeat known-good steps and makes the case much faster to isolate.

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.