QC Dynamic Replacer Post-Upgrade Verification Checklist

After upgrading QC Dynamic Replacer to 1.1.05, verify more than the Joomla success message. Check package-member versions, preserved configuration, runtime and entitlement automation, updater state, and representative frontend behavior before closing the maintenance window.

Confirm the Package Upgrade Completed

  1. Open QC Dynamic Replacer → Status and confirm the installed version is 1.1.05.
  2. Confirm the package still owns the QCDR component, System plugin, and Task plugin.
  3. If Joomla reports a member missing or mismatched, reinstall the current outer package over the existing installation rather than uninstalling QCDR first.

The supported maintenance path is install-over-existing. The 1.1.05 installer has explicit uninstall guards so repair logic does not run while Joomla is actually removing the extension.

Verify Existing QCDR Data Was Preserved

QCDR 1.1.05 introduces no new local database schema change for the entitlement correction and is designed to preserve existing Rules, Tokens, settings, paid configuration, preview history, and replacement behavior. Spot-check important production Rules and Tokens after the upgrade instead of recreating them.

  • Open several Rules and confirm state, targeting, order, replacement source, and notes remain intact.
  • Open representative Tokens, including Joomla-data or PHP Tokens if used, and confirm their saved configuration remains present.
  • Do not delete preserved higher-tier configuration merely because Effective tier is temporarily Basic during entitlement troubleshooting.

Verify Runtime and Task Repair

The outer package postflight attempts to keep the QCDR System plugin enabled and repairs the canonical entitlement automation where possible. After the upgrade:

  • confirm the System plugin is enabled;
  • confirm exactly one published QC Dynamic Replacer Entitlement Revalidation task exists;
  • confirm its cadence is at least hourly and the Joomla scheduler is actually executing tasks; and
  • resolve any Status warning instead of assuming installer repair succeeded silently.

Verify Authorized-Domain Entitlement

Current paid access is keyless and resolves through Authorized Domains. Confirm the domain, Base tier, Effective tier, Verification state, Last checked value, and task integrity. If a legacy saved key is still displayed, treat it as compatibility state—not the normal 1.1.05 activation workflow.

An unused one-time 30-Day Max Preview should still be unused after an ordinary upgrade. QCDR starts that preview only through the explicit start action.

Verify Update Discovery

Use Check for Updates on Status and confirm QCDR can synchronize its package-owned Joomla update site. Version 1.1.05 removes the obsolete package dlid dependency; current update discovery is aligned with the Authorized-Domain model.

Verify Live Behavior Without Broadly Changing State

  • Confirm the Rules and Tokens Live Processing switches have the intended values.
  • Test a known direct Rule and a known Token on representative frontend pages.
  • For saved Rules that justify extra caution, use Preview & Rule Health before changing their live state.
  • If you use Discovery, confirm a private session can launch under the intended account.
  • If you publish the frontend Dynamic Replacer Workspace, open it with the same user classes that rely on it and confirm the readiness counts look reasonable.

Close the Upgrade Only After Frontend Verification

Clear or bypass relevant caches, request representative pages again, and compare the result with your pre-upgrade baseline. If something differs, collect Status, Rule Health, and Support Information evidence before making multiple unrelated changes. The safest repair remains installing the current package over the existing installation unless QuantaCade support specifically directs otherwise.

Community Discussion

Want to compare workflows, share practical tips, or discuss how you use this QCDR feature? Visit the QC Dynamic Replacer Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.