QCUI 1.0.03 Requirements and Prerequisites
QCUI 1.0.03 Requirements and Prerequisites 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.
Required conditions
| Requirement | Why it matters |
|---|---|
| Supported Joomla installation | QCUI is a Joomla System plugin and depends on Joomla users, sessions, ACL, plugin events and form tokens. |
| Super User issuer | Only identities with core.admin receive the launcher and may start a handoff. |
| Shared Sessions disabled | QCUI refuses operation when Joomla shares site and administrator sessions because an identity switch could endanger the admin session. |
| Eligible target | The target must exist, differ from the issuer, not be blocked/reset-required/Super User, and have core.login.site. |
| Working sessions/cookies | Frontend session forking and the joomla_user_state cookie must function normally. |
No external service dependency
QCUI 1.0.03 performs impersonation locally inside Joomla. It does not require a QuantaCade license server, Scheduled Task, external callback, or customer password. Joomla update discovery uses the QuantaCade update XML, but runtime impersonation itself is local.
Operational context
For QCUI 1.0.03 Requirements and Prerequisites, 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.