Why the Internal qcloginasuser Element Is Retained

Why the Internal qcloginasuser Element Is Retained is a deliberate QCUI 1.0.03 behavior that protects administrator access, target-account safety, or the integrity of the one-time impersonation handoff.

Upgrade identity

Joomla identifies the System plugin internally as qcloginasuser. QCUI keeps that element even though the public name is QC User Impersonation.

Why renaming would be risky

Changing the element during a normal product rename could cause Joomla to treat the release as a different plugin, leaving duplicates or breaking schema/update continuity.

Where you see it

  • Plugin manifest/services/media paths.
  • Database table prefix #__qcloginasuser_*.
  • Update server file name qcloginasuser.xml.
  • Internal session/form keys use the shorter qclau prefix.

Maintenance boundary

Why the Internal qcloginasuser Element Is Retained 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

Why the Internal qcloginasuser Element Is Retained 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.