QC Dynamic Replacer Requirements Before Installation

Supported Joomla/PHP baseline, normal Joomla package installation, frontend HTML processing assumptions, Administrator access, Scheduled Tasks, and update-site connectivity.

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.

Supported Joomla/PHP baseline

QCDR has one canonical entitlement task routine, qc_dynamic_replacer.license_revalidation, and the current security boundary expects it to run hourly. Missing, disabled, unpublished, duplicated, or intentionally slowed task state is treated as an integrity problem and can force Effective Basic until repaired. The task refreshes server-authoritative entitlement; it does not start an unused Max Preview. On quiet Joomla sites, the task definition can be healthy while execution is late because Joomla still needs a trigger, which is why QC Task Nudge & Health is the recommended companion for scheduler visibility and wake-up assistance.

For QC Dynamic Replacer Requirements Before Installation, 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.

Normal Joomla package installation

QCDR has one canonical entitlement task routine, qc_dynamic_replacer.license_revalidation, and the current security boundary expects it to run hourly. Missing, disabled, unpublished, duplicated, or intentionally slowed task state is treated as an integrity problem and can force Effective Basic until repaired. The task refreshes server-authoritative entitlement; it does not start an unused Max Preview. On quiet Joomla sites, the task definition can be healthy while execution is late because Joomla still needs a trigger, which is why QC Task Nudge & Health is the recommended companion for scheduler visibility and wake-up assistance.

For QC Dynamic Replacer Requirements Before Installation, 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.

Frontend HTML processing assumptions

QCDR has one canonical entitlement task routine, qc_dynamic_replacer.license_revalidation, and the current security boundary expects it to run hourly. Missing, disabled, unpublished, duplicated, or intentionally slowed task state is treated as an integrity problem and can force Effective Basic until repaired. The task refreshes server-authoritative entitlement; it does not start an unused Max Preview. On quiet Joomla sites, the task definition can be healthy while execution is late because Joomla still needs a trigger, which is why QC Task Nudge & Health is the recommended companion for scheduler visibility and wake-up assistance.

Administrator access

QCDR has one canonical entitlement task routine, qc_dynamic_replacer.license_revalidation, and the current security boundary expects it to run hourly. Missing, disabled, unpublished, duplicated, or intentionally slowed task state is treated as an integrity problem and can force Effective Basic until repaired. The task refreshes server-authoritative entitlement; it does not start an unused Max Preview. On quiet Joomla sites, the task definition can be healthy while execution is late because Joomla still needs a trigger, which is why QC Task Nudge & Health is the recommended companion for scheduler visibility and wake-up assistance.

Scheduled Tasks

QCDR has one canonical entitlement task routine, qc_dynamic_replacer.license_revalidation, and the current security boundary expects it to run hourly. Missing, disabled, unpublished, duplicated, or intentionally slowed task state is treated as an integrity problem and can force Effective Basic until repaired. The task refreshes server-authoritative entitlement; it does not start an unused Max Preview. On quiet Joomla sites, the task definition can be healthy while execution is late because Joomla still needs a trigger, which is why QC Task Nudge & Health is the recommended companion for scheduler visibility and wake-up assistance.

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

  • The current account has Manage PHP Tokens and the Effective tier permits PHP.
  • Normal production error mode is Hide unless a temporary sanitized diagnostic is intentionally active.
  • 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

  • Treating PHP Tokens as sandboxed snippets or granting Manage PHP Tokens more broadly than necessary.
  • 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.