How the QuantaCade QCUI Update Server Is Used

How the QuantaCade QCUI Update Server Is Used describes a current QCUI 1.0.03 implementation detail that matters when you are validating security, session isolation, or support behavior.

Manifest update source

The plugin manifest registers https://quantacade.com/updates/qcloginasuser.xml as System - QC User Impersonation Updates. Joomla uses this metadata for extension update discovery.

Runtime is separate

The update server is not contacted to authorize each impersonation. QCUI runtime is local and free; there is no license/entitlement validation service in the handoff flow.

If update discovery fails

Troubleshoot Joomla Update Sites, outbound HTTPS/DNS, caches and the QuantaCade update metadata. Do not look for a license key field because none exists.

Maintenance boundary

How the QuantaCade QCUI Update Server Is Used should be handled through Joomla’s extension installer/update lifecycle. The retained qcloginasuser identity, schema migrations, and uninstall SQL exist to make that lifecycle predictable; manual file/table surgery can create a state the released plugin was not designed to manage.

Maintenance boundary

How the QuantaCade QCUI Update Server Is Used should be handled through Joomla’s extension installer/update lifecycle. The retained qcloginasuser identity, schema migrations, and uninstall SQL exist to make that lifecycle predictable; manual file/table surgery can create a state the released plugin was not designed to manage.

Community Discussion

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