QCFUM Production Go-Live and Update Checklist

Use this checklist before putting QC Frontend User Manager into production and after installing a QCFUM update. Test the workflows the site actually uses, beginning with the security and entitlement foundations before moving into higher-tier features.

The current documentation baseline for this checklist is QCFUM 2.0.4.

Before Installation or Update

  • Create a current Joomla/database backup and confirm you can restore it.
  • Confirm the package version you intend to install and retain the previous working package when practical.
  • Identify which QCFUM frontend tabs, administrator settings, Profiles, Invite Packs, Join Codes, approval rules, automation jobs, and Frontend User Manager actions the site actually uses.

Verify the Foundation After Installation

  1. Open QCFUM Status and confirm the active package/version, Authorized-Domain entitlement state, Base/Effective tier, and a healthy Entitlement Revalidation task.
  2. Confirm the QCFUM task plugin and Joomla Scheduled Tasks runner are operating.
  3. Open the unified frontend Dashboard with the exact non-admin staff account that will use it. Verify menu access and only the intended per-tab ACL actions.
  4. Review User Type Profiles and Invite Packs, including publication state and destination Joomla groups.
  5. Review administrator notification recipients and send a controlled email test through the configured Joomla mail transport.

Smoke-Test by Tier

Basic: Direct Create, Invite Links, Recent Users/Tracker, and the site’s frontend text/appearance. Pro: add CSV, approvals, temporary access, Custom HTML, and any enabled Scheduled Automation/retry jobs. Max / All Access: add Join Codes, Frontend User Manager target protection/action gates, and Custom CSS.

Protect the Frontend User Manager

Before enabling delegated management, verify source groups, editable groups, allowed destination groups, explicitly excluded users/groups, current-user protection, and administrator-recipient protection. Test with a real non-admin manager and a disposable non-privileged target before touching production accounts.

Account for Current 2.0.4 Limitations

Do not use Bulk Actions as a go-live requirement in 2.0.4: the current handler rejects the bulk request before its bulk loop. Also remember that unified Recent Users count mode is bypassed by its 1000-row request, and durable User Manager approval rows are acted on from Approval Queue rather than the Administrator Tracker.

After Future Updates

Re-run the foundation checks and smoke-test only the workflows the site uses. Pay special attention to task health, entitlement, ACL, Profiles/Packs, mail, approval paths, and any source-confirmed limitation that a newer release claims to correct.

Community Discussion

Want to compare Joomla user-management workflows, share practical QCFUM tips, or discuss how other administrators use this feature? Visit the QC Frontend User Manager Community. For private support, bug reports, account-specific entitlement problems, or feature requests, use the QuantaCade support system.