Edit, Publish, Unpublish, or Delete a Join Code
Join Codes are durable configuration records. Editing or unpublishing one changes whether it can be used now; deleting it removes the reusable code record. None of those actions should be confused with entitlement loss or with deletion of Joomla users previously created through the code.
QCFUM requires the current Max/All Access Join Code feature for save and delete actions. A downgrade preserves existing code records so they can become usable again if entitlement returns.
Edit an Existing Code
Use the Join Codes table Edit action. You can change the title, normalized code value, Invite Pack, usage limit, expiration date, and Published state. The edit form carries the current used_count in a hidden field so normal edits preserve accumulated use history.
Unpublish Instead of Deleting When You May Reuse It
Setting Published off immediately removes the code from the currently usable Join Code query and loadJoinCodeByCode() will no longer load it for completion. The record, usage count, Pack relationship, and expiration value remain stored.
Delete Removes the Reusable Code Record
Delete removes the row from #__qcfum_join_codes and records an audit event. Created-user history stores its own Join Code ID/source context; deleting the code does not delete the Joomla accounts or the created-user history rows.
Downgrade Is Different
If the Effective tier drops below Max, Join Code save/delete operations are locked because the feature is unavailable. Existing rows remain in storage. After Max/All Access returns, a preserved published code can be usable again only if its current expiration, usage limit, Pack, and Profile checks also pass.
Safe Lifecycle Practice
- Unpublish a code before retiring it.
- Confirm no current workflow still depends on it.
- Keep it unpublished if you may need the configuration/history again.
- Delete only when the reusable record itself is no longer needed.
Community Discussion
Want to compare Joomla user-onboarding 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.