What QCUI Removes from the Database During Uninstallation
What QCUI Removes from the Database During Uninstallation explains the current QCUI 1.0.03 behavior and how it affects a Super User who needs to inspect the Joomla frontend as an eligible user.
Removed data
- System plugin files/media/language through Joomla extension uninstall.
#__qcloginasuser_tokens.#__qcloginasuser_audit.
What is not a QCUI-owned credential
There is no QCUI license key or target password table to clean up. Joomla user accounts themselves are not removed by uninstalling QCUI.
Plan before uninstall
End active support sessions and retain any audit evidence your organization requires before Joomla executes the uninstall SQL.
Maintenance boundary
What QCUI Removes from the Database During Uninstallation 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
What QCUI Removes from the Database During Uninstallation 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.