QC Dynamic Replacer Entitlement Revalidation Scheduled Task

Canonical qc_dynamic_replacer.license_revalidation routine, hourly cadence, server-side entitlement refresh, no preview auto-start, and why normal frontend transformation does not wait for the task.

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

Save the Rule first, even if it remains Draft or Disabled.
Confirm your Joomla account has Test Rules and the current tier includes private Preview.
Enter a same-site frontend URL that represents the intended Rule target.
Launch Preview from the Rule editor and inspect the private transformed page.
Read Rule Health for state/tier, target, audience, schedule, dependency, match, and protected-region gates.
Correct the Rule and relaunch Preview rather than enabling it just to test.
After successful private testing, enable the Rule only if ordinary runtime behavior is desired.

Canonical qc_dynamic_replacer.license_revalidation routine

QCDR 1.1.05 uses the current keyless Authorized-Domain entitlement model. Basic remains the fallback feature set, while paid Pro/Max and All Access are resolved from the normalized Authorized Domain rather than a customer-entered current license key. The one-time 30-Day Max Preview starts only when an authorized administrator explicitly selects Start 30-Day Max Preview; installation, navigation, Refresh Entitlement, frontend requests, and the Scheduled Task do not consume an untouched preview. Base tier and Effective tier remain separate so All Access or Preview can temporarily elevate capability without rewriting the underlying product state. Upgraded sites can still show a Legacy License Key, but clearing it is a compatibility cleanup action and must preserve Rules, Tokens, settings, preview history, and current Authorized-Domain state.

For QC Dynamic Replacer Entitlement Revalidation Scheduled Task, 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.

Hourly cadence

Server-side entitlement refresh

No preview auto-start

And why normal frontend transformation does not wait for the task

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

Status shows the expected Base and Effective tiers for the normalized domain.
Entitlement Revalidation is healthy and hourly unless the article is specifically diagnosing that task.
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

Enabling a broad Rule for ordinary visitors merely to test something private Preview can validate safely.
Ignoring timezone/DST or inventing syntax for the reserved Custom recurrence field.
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.