What to Include in a QCLF Support Request and Current Terminology
A useful QCLF support request gives enough exact, non-secret context to reproduce the failing layer without exposing credentials or private member/guest information. Start with the current version, exact action, role, Topic/live type, entitlement/task state, and the first visible error.
The QCLF Support tab already exposes a deliberately safe support summary and links to QuantaCade support/resources.
Include This Reproduction Context
- Product/version: QC Live Forum and the installed version shown on Support/Status.
- Exact action: what you clicked/submitted, what you expected, and what actually happened.
- Location: the safe frontend/admin route or view, plus Section/Category/Topic IDs or titles when relevant. Remove any secret-bearing query data.
- User role: administrator, moderator scope, exact Host, signed-in member, guest, or viewer. State whether a second account/device reproduces it.
- Topic/live context: Traditional Topic, Live Chat, Watch Party, or Live Broadcast; include current lifecycle state/times and session/topic IDs when useful.
- Entitlement/automation: Base tier, Effective tier, verification mode/status, and relevant Scheduled Task health/last result.
- Environment/error: Joomla/PHP/browser/device details when relevant, exact error text, and a cropped screenshot or log excerpt that excludes secrets/private identities.
Use the Safe Support Summary
The Administrator Support tab shows Product, Version, Product code, Domain, a masked saved Legacy License Key (if any), entitlement Status, Effective tier, and Installation UUID. Its own note explicitly omits full license keys, tokens, credentials, private server paths, and secret-bearing request data. Use that same standard when collecting screenshots.
Do Not Include
- Passwords, full Legacy License Keys, installation signing keys, access tokens, short-lived Host Live room credentials, API/service secrets, or private server filesystem paths.
- Private guest identity metadata, private email/IP information, or unrelated member data in public/community posts.
- Large database exports or full configuration files when a small redacted record/state summary will reproduce the issue.
Current QCLF Terminology
| Current term | Meaning |
|---|---|
| Section → Category → Topic → Message | Durable QCLF community/content hierarchy. |
| Traditional Topic | The normal discussion Topic type; permanent chronological conversation. |
| Live Chat | Basic+ live Topic whose eligible chat becomes permanent history. |
| Watch Party | Max/All Access synchronized YouTube live Topic; exact Host controls sync. |
| Live Broadcast | Pro+ one-Host managed live-media Topic; viewers receive media; Host A/V is not recorded/replayed. |
| Host Live | Managed short-lived camera/microphone transport used by Watch Party/Broadcast; not permanent server credentials. |
| Authorized Domains | Current paid-entitlement mechanism. |
| Legacy License Key | Backward-compatibility data only; not the current activation workflow. |
| Base tier / Effective tier | Underlying entitlement versus the tier currently usable after All Access/Preview/task-health rules. |
| 30-Day Max Preview | One-time explicit administrator-started Max Preview; not auto-started by install/page views/tasks. |
| Scheduled Tasks | Entitlement Revalidation, Live Lifecycle Reconciliation, Live Archive Conversion, Notification Delivery, and Cleanup. |
Where to Send It
Use the QuantaCade Support area for private account/site-specific problems. Use the QCLF Community for non-private workflow discussion after removing secrets and personal information.
Community Discussion
Want to compare forum workflows, share practical QCLF tips, or discuss how other Joomla site owners use this feature? Visit the QC Live Forum Community. For private support, bug reports, account-specific entitlement problems, or feature requests, use the QuantaCade support system.