QC Live Forum Live Broadcast Requirements and Pro/Max Entitlement

Confirm effective tier, Category capability, creation permission, browser media permissions, and current live-service availability.

This guide follows the accepted QC Live Forum 1.1.27 implementation and applies to Pro / Max / All Access. Live Broadcast adds managed one-Host live media to a durable QCLF Topic; viewers receive media and may participate in chat according to normal Category and moderation rules. When older walkthrough or project-manual wording conflicts with 1.1.27 source or later accepted Authorized-Domain behavior, the current implementation takes precedence.

Before You Begin

• Confirm Effective Pro, Max, or All Access plus the Category Live Broadcast capability.
• Grant browser camera/microphone permission only to the Host device you intend to use.
• Test the viewer experience from a separate non-Host account before a real event.

Current QCLF Behavior

Step-by-Step Workflow

1. Open QC Live Forum in Joomla Administrator and review the shared entitlement notice and Status tab.
2. Confirm the site's current domain is authorized in the QuantaCade account when paid access is expected.
3. Use the provided entitlement action only for the intended operation: refresh current entitlement, clear a Legacy License Key, or explicitly start the one-time 30-Day Max Preview.
4. Reopen Status and compare Base tier with Effective tier; do not overwrite one concept with the other.
5. Check the QC Live Forum Entitlement Revalidation Scheduled Task if premium controls unexpectedly fall back to Basic.
6. Verify the affected paid feature from the real frontend using the intended user role.

Confirm effective tier, Category capability, creation permission, browser media permissions, an

Confirm effective tier, Category capability, creation permission, browser media permissions, and current live-service availability is part of the current QCLF 1.1.27 behavior. Treat the current server-side state as authoritative: frontend controls are useful guidance, but QCLF still rechecks Joomla access, QCLF action permissions, feature state, entitlement, and the target object's current status when the action is submitted.

When access is involved, test both an allowed and denied account. Joomla view levels determine whether a user can reach a surface, while QCLF's own Section/Category/action rules determine what that user may actually do there. Inherited group rules and moderator scope should be verified with the same Joomla groups used in production.

How This Fits into QC Live Forum

Live Broadcast adds managed one-Host live media to a durable QCLF Topic; viewers receive media and may participate in chat according to normal Category and moderation rules. A reliable configuration keeps Joomla authoritative for users, groups, access levels, sessions, mail transport, and Scheduled Tasks while QCLF owns forum structure, Topic/Message state, personalization, live-session state, moderation records, and feature-specific rules. Keeping those responsibilities separate makes troubleshooting much faster.

For QC Live Forum Live Broadcast Requirements and Pro/Max Entitlement, verify the behavior with the role that will actually use it. Administrator, moderator, Host, signed-in member, guest, and viewer experiences intentionally differ. A successful test as Super User does not prove that a normal member or delegated moderator has the correct access.

Permissions, Entitlement, and Safety

• Joomla menu/view access, QCLF Section/Category access, QCLF action permissions, moderation scope, and commercial feature entitlement are separate checks.
• QCLF re-authorizes state-changing requests server-side; never treat a visible or hidden frontend control as the security boundary.
• Use Authorized Domains for current paid entitlement. Legacy License Key data is compatibility history and should not be reintroduced as the current activation workflow.
• Premium records and settings are preservation-first across downgrade; loss of current Effective tier can disable use without deleting the saved configuration.
• Do not expose passwords, saved keys, private managed-service credentials, or private guest identity data in public forum content, screenshots, or support posts.
• When a paid feature is missing unexpectedly, check Effective tier and the hourly Entitlement Revalidation task before rebuilding the feature configuration.

Verify the Result

• The Host can start media and choose the expected camera/microphone.
• A viewer receives Host media without receiving publishing controls.
• Live chat, moderation, reconnect, extend, and End behavior remain functional during the broadcast.
• After End, Host media is gone and chat archive conversion produces permanent forum history once.

Common Mistakes to Avoid

• Expecting ordinary viewers to publish media.
• Assuming a temporary reconnect state means the server-authoritative session is still live after End.
• Sharing or troubleshooting with permanent transport credentials; QCLF uses short-lived managed credentials.
• Expecting recorded video replay from a completed broadcast.

Troubleshooting

• Reproduce the exact action with the smallest safe test and note the user role, Section/Category, Topic type, and current state.
• If a control is missing, check access, QCLF permissions, feature inheritance, Topic state, and Effective tier in that order before assuming files are damaged.
• If a live or notification action is delayed, inspect the appropriate Scheduled Task and current lifecycle/delivery state instead of manually duplicating the work.
• If only one browser/device fails during live media, test browser permissions, autoplay/media policy, and network conditions before changing server configuration.
• After a correction, rerun the same test and reload the real frontend page; a saved Administrator form message alone is not end-to-end verification.

Operational Best Practice

Keep the forum model understandable: use the fewest permission and feature overrides needed, give moderators the narrowest useful scope, test live features with separate Host/viewer accounts, and keep Scheduled Tasks healthy. Before a major QCLF or Joomla update, maintain a current backup and a simple regression checklist covering Discussion, Search, Following, notifications, moderation, and every live Topic type you actively use.

Community Discussion

Want to compare community 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.