Read QCDR Rule Health Diagnostics

Health checks for state/tier, page/menu/extension, audience, schedule, IP, technical conditions, Token readiness, match/replacement readiness, protected areas, and final eligibility.

This guide follows the accepted QC Dynamic Replacer 1.1.05 implementation and applies to Pro / Max / All Access + Test Rules 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

Save the Rule first; Preview/Rule Health works from a saved Rule identity.
Use only a same-site frontend URL.
Keep the private test authorization fresh and do not mistake a Preview result for ordinary visitor state.

Step-by-Step Workflow

Save the Rule and choose a representative same-site frontend URL.
Launch private Preview from an authorized account.
Read Rule Health gate-by-gate.
Correct the smallest failing condition or match definition.
Retest privately before changing the normal Rule state.

Condition Vocabulary

Current technical conditions can inspect URL, menu, component, view, language, user group, template, hostname, query, request method.

Supported comparison operators include equals, not_equals, contains, not_contains, starts_with, ends_with, matches, in, not_in. Use All logic when every condition must pass, or Any logic when one passing condition is sufficient.

Health checks for state/tier

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 Read QCDR Rule Health Diagnostics, 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.

Page/menu/extension

Audience

Schedule

IP

How This Fits into QCDR

Preview and Rule Health are private diagnostics. They do not need to enable the Rule for ordinary visitors.

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

The Rule state and drag order are exactly what you intended.
A page that should match changes as expected, and a page outside scope remains unchanged.
The Token resolves where it is eligible and preserves authored content where it is intentionally unavailable.
Reference/dependency behavior is understood before deleting or downgrading a Token.
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

Assuming an unavailable Token should become an empty string; QCDR often preserves the original placeholder or Rule match intentionally.
Trusting forwarded client-IP headers without restricting which proxy/CIDR is allowed to supply them.
Ignoring timezone/DST or inventing syntax for the reserved Custom recurrence field.
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.