What Changed in QC User Impersonation 1.0.03

What Changed in QC User Impersonation 1.0.03 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.

1.0.03 change

QCUI 1.0.03 corrects fresh-install auto-enable compatibility with Joomla’s installer API. The installer script now obtains DatabaseInterface through Joomla’s dependency-injection container instead of attempting to call a protected installer-adapter database method.

What did not change

The 1.0.03 schema migration explicitly contains no database schema changes. The impersonation security/session model and the existing token/audit table shape remain intact.

Upgrade impact

Existing installations update in place under the retained qcloginasuser element and preserve the current enabled/disabled state.

Maintenance boundary

What Changed in QC User Impersonation 1.0.03 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 Changed in QC User Impersonation 1.0.03 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.