Why QCUI Enables Itself After a Fresh Installation

Why QCUI Enables Itself After a Fresh Installation is a deliberate QCUI 1.0.03 behavior that protects administrator access, target-account safety, or the integrity of the one-time impersonation handoff.

Fresh-install behavior

QCUI 1.0.03 installer code explicitly enables the system/qcloginasuser plugin during the initial Joomla installation. It obtains Joomla’s database service through the dependency-injection container, which is the compatibility correction delivered in 1.0.03.

Update behavior is different

The installer’s update() path does not force-enable the plugin. That preserves an administrator’s existing enabled/disabled choice across upgrades. A disabled production plugin should therefore remain disabled after updating unless you deliberately enable it.

Verify the result

• After a fresh install, System - QC User Impersonation is enabled.
• After an upgrade, the pre-upgrade enabled/disabled state remains your administrative choice.

Operational context

For Why QCUI Enables Itself After a Fresh Installation, remember that QCUI has no separate component dashboard or remote authorization service. The System plugin owns the launcher/handoff/banner behavior locally inside Joomla. If what you see differs from these instructions, verify the installed plugin version and active Joomla template/session configuration before assuming another QCUI screen or service exists.

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.