Using QCUI to Troubleshoot Module Visibility

Using QCUI to Troubleshoot Module Visibility is a practical QCUI 1.0.03 workflow. Follow the current Joomla path and verify the resulting administrator/frontend state rather than relying on an older impersonation method.

Support workflow

  1. Identify the exact frontend behavior or permission you need to verify.
  2. From Joomla Administrator, start QCUI for an eligible user who represents the affected account or ACL state.
  3. In the separate frontend tab, navigate to the specific menu, module, page, form, profile, membership, portal, or extension workflow under test.
  4. Record what is visible/allowed and compare it with the intended Joomla groups, access levels, menu/module assignments, or extension rules.
  5. End impersonation before making unrelated changes; after changing permissions/configuration, start a fresh or clearly controlled retest.

What to compare

For Troubleshoot Module Visibility, compare the target user’s visible navigation and permitted actions with the intended Joomla user groups, access levels, menu/module assignments, and any extension-specific rules. QCUI shows the effective frontend result; it does not explain or override the underlying ACL decision.

Avoid false conclusions

Module visibility can depend on access level, menu assignment, template position, language, publishing state, and extension conditions. Compare those controls before treating a missing module as a user-session problem.

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.