Troubleshoot QCDR Page Targeting, Scheduling, IP, Conditions, and Caching

Layered eligibility diagnosis, timezone/blackout recurrence, trusted proxies, condition syntax, all-vs-any, menu/URL scope, audience, and cached variants.

This guide follows the accepted QC Dynamic Replacer 1.1.05 implementation and applies to All plans; advanced controls require Pro/Max. 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

Capture the exact affected URL, Rule/Token state, tier, and visible result before changing multiple settings.
Use Rule Health/Discovery evidence where available instead of guessing at origin or eligibility.
Never include license secrets, arbitrary PHP secrets, credentials, or private customer data in public support material.

Step-by-Step Workflow

Reproduce the issue on one known frontend URL and record the exact visible result.
Check QCDR version, Base/Effective tier, and Status/task health before changing content.
Check the relevant Rule/Token state and the matching Live Processing switch.
Review every applicable target gate in order: page, extension, audience, schedule, IP, conditions, dependencies, protected areas.
Use Rule Health, Preview, or Discovery evidence where your plan/permissions allow it.
Eliminate cache/CDN effects before concluding that QCDR did not process the request.
Change one setting at a time and retest so the actual cause remains identifiable.

Layered eligibility diagnosis

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 Troubleshoot QCDR Page Targeting, Scheduling, IP, Conditions, and Caching, 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.

Timezone/blackout recurrence

Trusted proxies

Condition syntax

All-vs-any

How This Fits into QCDR

Troubleshooting should isolate one eligibility gate or runtime boundary at a time and preserve a known-good recovery path.

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

Trusting forwarded client-IP headers without restricting which proxy/CIDR is allowed to supply them.
Testing personalized output through a shared page/CDN cache and assuming the cached result reflects current eligibility.
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.