Understand QCDR Custom Recurrence as a Reserved Field

Current UI exposes a Custom recurrence field but explicitly reserves its syntax for future documentation; do not invent unsupported syntax or rely on undocumented rules.

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

  • Start with the narrowest page scope that proves the use case.
  • Account for Joomla caching/CDN behavior before relying on audience or IP-specific output.
  • Use Preview/Rule Health for complicated gate combinations whenever available.

Step-by-Step Workflow

  1. Open the Rule or Token and identify its current broad scope.
  2. Add the narrowest targeting gate required for the use case.
  3. Save and test both a request that should pass and one that should fail.
  4. Use Rule Health for layered gate diagnosis when available.
  5. Review caches when the target varies by visitor or request context.

UI exposes a Custom recurrence field but explicitly reserves its syntax for

Pro scheduling can keep an item Always active, limit it to an overall start/end range, or apply recurring daily/weekly/monthly behavior with repeat interval, weekday/day-of-month controls, an optional daily active window, timezone selection, and blackout dates. QCDR compares the request time using the configured/site timezone rules while preserving overall boundaries. The visible Custom recurrence field is reserved; current documentation must not invent a syntax that the product has not defined for customers.

For Understand QCDR Custom Recurrence as a Reserved Field, 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.

Do not invent unsupported syntax or rely on undocumented rules

Pro scheduling can keep an item Always active, limit it to an overall start/end range, or apply recurring daily/weekly/monthly behavior with repeat interval, weekday/day-of-month controls, an optional daily active window, timezone selection, and blackout dates. QCDR compares the request time using the configured/site timezone rules while preserving overall boundaries. The visible Custom recurrence field is reserved; current documentation must not invent a syntax that the product has not defined for customers.

For Understand QCDR Custom Recurrence as a Reserved Field, 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.

How This Fits into QCDR

Targeting gates stack. A Rule or Token must pass every required gate in its current tier before it is eligible.

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.
  • 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.