Use the QCDR Support Tab and Gather Safe Support Information

Support/Profile/Downloads/manual links, version/product/domain/installation information, masked legacy key state, server environment fields, and sensitive-data boundaries.

This guide follows the accepted QC Dynamic Replacer 1.1.05 implementation and applies to All plans; administrator. 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

  • Confirm you are working in Joomla Administrator with the permissions required for the action.
  • Record the current QCDR version and Base/Effective entitlement before changing licensing or task state.
  • Do not uninstall a working QCDR installation merely to update it; normal updates are install-over-existing.

Step-by-Step Workflow

  1. Open the QCDR Administrator area that owns this setting or status.
  2. Record the current version, entitlement, and task state before changing anything.
  3. Make the smallest required change and save it.
  4. Reload the owning screen and confirm the current value/status.
  5. Test a representative frontend request if the change can affect runtime output.

Support/Profile/Downloads/manual links

This behavior is evaluated inside the current QCDR 1.1.05 rendered-output pipeline. Treat the saved Rule or Token as only one part of eligibility: item state, Effective tier, targeting, schedule, request context, Live Processing controls, dependencies, protected regions, and runtime safety can all affect the final response. Verify the result on the actual frontend request rather than assuming that a successfully saved Administrator form guarantees runtime output.

For Use the QCDR Support Tab and Gather Safe Support Information, 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.

Version/product/domain/installation information

This behavior is evaluated inside the current QCDR 1.1.05 rendered-output pipeline. Treat the saved Rule or Token as only one part of eligibility: item state, Effective tier, targeting, schedule, request context, Live Processing controls, dependencies, protected regions, and runtime safety can all affect the final response. Verify the result on the actual frontend request rather than assuming that a successfully saved Administrator form guarantees runtime output.

For Use the QCDR Support Tab and Gather Safe Support Information, 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.

Masked legacy key state

This behavior is evaluated inside the current QCDR 1.1.05 rendered-output pipeline. Treat the saved Rule or Token as only one part of eligibility: item state, Effective tier, targeting, schedule, request context, Live Processing controls, dependencies, protected regions, and runtime safety can all affect the final response. Verify the result on the actual frontend request rather than assuming that a successfully saved Administrator form guarantees runtime output.

Server environment fields

This behavior is evaluated inside the current QCDR 1.1.05 rendered-output pipeline. Treat the saved Rule or Token as only one part of eligibility: item state, Effective tier, targeting, schedule, request context, Live Processing controls, dependencies, protected regions, and runtime safety can all affect the final response. Verify the result on the actual frontend request rather than assuming that a successfully saved Administrator form guarantees runtime output.

And sensitive-data boundaries

This behavior is evaluated inside the current QCDR 1.1.05 rendered-output pipeline. Treat the saved Rule or Token as only one part of eligibility: item state, Effective tier, targeting, schedule, request context, Live Processing controls, dependencies, protected regions, and runtime safety can all affect the final response. Verify the result on the actual frontend request rather than assuming that a successfully saved Administrator form guarantees runtime output.

How This Fits into QCDR

This category establishes the installation and entitlement foundation. It does not change Rule or Token content unless an article explicitly says so.

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.