What to Include in a QCFUM Support Request
A good QCFUM support request should make the exact workflow and environment reproducible without exposing credentials or secure onboarding data. QCFUM’s Administrator Support tab already presents a non-secret environment snapshot specifically intended to help with support.
Include enough context to identify the failing gate, but never send passwords, Invite tokens, entitlement tokens, database credentials, or other private secrets.
Start with the Exact Product and Workflow
- QCFUM version and Joomla version.
- The exact frontend Dashboard tab or administrator tab involved.
- The action you attempted and the exact button/setting used.
- What you expected, what actually happened, and the complete error/message text.
- Whether the problem happens every time and the shortest reproducible sequence.
Include the Non-Secret Support Snapshot
The Support tab exposes Product, Version, Product code, Domain, masked saved-key history, entitlement Status, Effective tier, Installation UUID, Joomla/PHP/SAPI/database information, OpenSSL, cURL, PHP HTTPS streams, memory/execution limits, Joomla mail transport, HTTPS state, Scheduled Tasks strategy, scheduler runner, QCFUM task plugin, and basic server software/hostname information. QCFUM intentionally omits secret values, full credentials, tokens, password data, and private server paths.
Add Workflow-Specific Context
| Problem area | Useful non-secret evidence |
|---|---|
| Frontend User Manager | Manager account role/ACL, target user ID or username, relevant Joomla groups, View-only/editable state, configured action, and whether the target is intentionally protected. |
| Scheduled Tasks / entitlement | Task type, publication state, cadence, last/next execution, last exit code, Status-tab health message, and whether Joomla has an active scheduler runner. |
| Template key/title, publication state, recipient type, queue row status/attempt count/last error, Joomla mail transport, and whether Send Test succeeds. | |
| CSV | Header row, row count/file size, Direct-vs-Invite mode, default Profile/Pack, preview result and exact invalid-row message. Remove personal data that is not needed to reproduce the problem. |
| Join Codes / Invite Links | Record ID/title/status, Pack/Profile names, expiration/remaining-use state, and exact refusal. Do not include the actual secure Invite token. |
Screenshots and Logs
Attach screenshots that show the relevant QCFUM state and exact message. If Joomla/PHP logs contain the failure, include the small relevant excerpt and timestamp rather than an unrelated full server log. Redact unrelated personal information and credentials.
Never Include Secrets
Do not send Joomla or hosting passwords, temporary passwords generated for users, Invite Link tokens, Join Code secrets that should remain private, license/entitlement API tokens, database/FTP/SSH credentials, private keys, or unredacted configuration files. The Support snapshot is designed to provide useful diagnostics without those values.
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.