Legacy License Keys in QCFUM: Display, Clear, and Migration Behavior

QCFUM 2.0.4 uses Authorized Domains for current paid entitlement. An older installation can still contain a saved license key, but Administrator presents it as a read-only Legacy License Key for compatibility with earlier QuantaCade releases.

Clearing that value is a migration cleanup action. It is not a QCFUM data reset.

Where a Legacy Key Appears

If QCFUM finds a saved legacy key, the Settings tab shows it in the Licensing & Entitlement card as a read-only value. There is no current workflow for pasting a replacement paid key into that field. Current Pro, Max, and All Access entitlement is resolved from Authorized Domains.

Clear the Saved Legacy Key

  1. Confirm the current site domain is authorized for QC Frontend User Manager in your QuantaCade account.
  2. Open Components > QC Frontend User Manager > Settings.
  3. In Licensing & Entitlement, review the Domain, Base tier, Effective tier, and Verification values.
  4. Select Clear Saved Key.
  5. Confirm the warning. QCFUM clears the local legacy credential and removes the old updater credential dependency.
  6. QCFUM immediately re-resolves entitlement for the Authorized Domain.

Possible Results After Clearing

  • If an Authorized Domain supplies Pro or Max, that paid tier remains available.
  • If All Access applies, QCFUM continues with Max-level product entitlement through the Authorized Domain/All Access source.
  • If an independently active 30-Day Max Preview exists, clearing the legacy key does not cancel that Preview.
  • If no paid Authorized-Domain entitlement or active Preview applies, QCFUM returns to Basic.

What Clear Saved Key Does Not Delete

The action clears the old local key; it does not delete QCFUM business/configuration tables, Profiles, Invite Packs, invitations, created-user history, email templates, Authorized Domains in your QuantaCade account, Preview history, or paid-claim history. QCFUM’s preservation-first design keeps configuration separate from current entitlement.

Why a Legacy Key Can Still Affect an Upgraded Site

For migration compatibility, QCFUM can fall back to validating a saved legacy key when the normal Authorized-Domain entitlement call returns Basic without a paid entitlement. That compatibility path is why it is useful to authorize the domain first and then deliberately clear the old key once the current model is working.

Verify the Migration

After clearing, return to Status. Verification should identify the current method—normally Authorized Domain, Authorized Domain + All Access, 30-Day Max Preview, or Basic. The Legacy License Key field should no longer appear once the saved value is gone.

Community Discussion

Want to compare Joomla user-onboarding workflows, share practical QCFUM tips, or discuss how other administrators use this feature? Visit the QC Frontend User Manager Community. For private support, bug reports, account-specific entitlement problems, or feature requests, use the QuantaCade support system.