Troubleshooting QCUI When the Plugin Is Installed but Disabled

Troubleshooting QCUI When the Plugin Is Installed but Disabled requires identifying whether the problem is in plugin visibility, target eligibility, the short-lived handoff, or the separate frontend session before changing configuration.

Diagnostic procedure

  1. Open System → Manage → Plugins.
  2. Enable System - QC User Impersonation.
  3. Save if Joomla presents an edit form.
  4. Reload Joomla Administrator as a Super User and confirm the launcher appears.
  5. If an upgrade disabled state was intentional, remember that QCUI updates preserve that administrator choice.

Keep the layers separate

This problem is still in the administrator/plugin-rendering layer. Confirm Super User authorization, plugin enabled state, injected assets, and administrator-template compatibility before investigating handoff tokens or frontend sessions.

Information to preserve

Preserve the QCUI enabled state, administrator account authorization, active administrator template, and whether QCUI CSS/JavaScript requests load.

When to escalate

If Troubleshooting QCUI When the Plugin Is Installed but Disabled persists after the documented layer is verified, stop creating repeated handoffs and preserve the exact error/context. A private support case should include version/state evidence but never passwords, session cookies, MFA secrets, or raw QCUI tokens.

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.