Legacy License Keys in QCDR: Display, Clear, and Migration Behavior
Current QCDR entitlement is based on Authorized Domains, not a pasted customer license key. A legacy key may still appear on an upgraded installation for compatibility, but it is read-only and should not be treated as the current activation method.
Where a Legacy Key Appears
If an older installation still has a saved key, QCDR can show a masked legacy-key value on Status and the Support Information card. Under Settings → Licensing & Entitlement, the saved legacy key is displayed read-only with a note that current paid entitlement comes from Authorized Domains.
If no legacy key is stored, QCDR does not show the Clear Saved Key action.
Clear the Saved Legacy Key
- Open QC Dynamic Replacer → Settings.
- Confirm that the site's current domain is authorized in your QuantaCade account if you expect paid QCDR access to continue.
- Click Clear Saved Key.
- Confirm the warning.
The action requires the QCDR Manage License permission.
What QCDR Clears
QCDR removes the local legacy-key value, its masked display value, the validated-key hash, and old key-bound cache/signature state. It also synchronizes the Joomla update site with an empty legacy credential so an old updater extra_query cannot rediscover and restore the key.
If the legacy key was still the active entitlement credential, QCDR first resets that key-bound entitlement state to Basic/pending before performing the current entitlement check.
Authorized Domain Entitlement Is Rechecked Immediately
After cleanup, QCDR immediately runs the current entitlement validation path. If the domain is properly authorized, Base/Effective tier is rebuilt from Authorized Domain entitlement. If no qualifying entitlement is available, QCDR remains safely on Basic.
A temporary connection problem follows the normal current entitlement rules; clearing a legacy key does not create a new key-based activation path.
What Is Preserved
Clear Saved Key does not delete Rules, Tokens, runtime settings, Discovery data, preview history, or customer configuration. The purpose is credential migration/cleanup, not product reset.
After clearing, verify Status → Current Entitlement and, if necessary, use Manage Authorized Domains and Refresh Entitlement.
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.