Troubleshoot Join Codes and Self-Service Registration

Join Codes are a Max / All Access onboarding path built on an Invite Pack and User Type Profile. A code can exist in the administrator list yet still be unusable because entitlement, publication, expiration, remaining uses, Pack/Profile state, or the public-registration setting blocks the current path.

Troubleshoot the dependency chain from plan → public/manager entry point → Join Code → Invite Pack → Profile → account identity rather than editing the code blindly.

If the Join Code Option Is Missing

Join Codes require Max/All Access. For the public guest path, Show Create With Join Code must be enabled. On the authenticated Dashboard, the Create User tab also requires qcfum.frontend.create; only currently usable Join Codes are offered in its selector.

If the Code Is Not Listed or Says Not Active

The code itself must be published, unexpired, and below its usage limit. Its Invite Pack and the Pack’s User Type Profile must both be published and available under the current tier. The frontend usable-code query enforces all of those conditions before listing a code.

If a Typed Code Fails During Registration

QCFUM normalizes the submitted code to uppercase letters, digits, underscore, and hyphen for lookup. It then rechecks publication, expiration, usage limit, the Pack/Profile mapping, and current Max feature access on the server. A stale browser page can therefore show a code that becomes unavailable before submission.

Understand the Usage-Reservation Message

Immediately before account creation QCFUM atomically increments used_count only if the code is still published, unexpired, and below its limit. If another registration consumes the last use first, the next request gets “no longer available.” If Joomla account creation then fails, QCFUM attempts to decrement the reserved use again.

Check the Account Data Last

After the code passes its own gates, normal account rules still apply: valid name/email, a non-conflicting email/username, matching password/confirmation, current created-user allowance where applicable, and Joomla User save success. Approval inherited from the Pack/Profile can create the account blocked/pending rather than immediately active.

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.