QCLF Production Go-Live Checklist

Verify entitlement/tasks, structure/access, Discussion, Search/Following/Notifications, Live Chat, paid live types, guest posting, email, mobile layouts, CSS, backup/update procedure.

This guide follows the accepted QC Live Forum 1.1.27 implementation and applies to All plans; administrator and moderator. QCLF uses Joomla Scheduled Tasks for security-sensitive entitlement refresh and unattended live/notification maintenance; troubleshooting should identify the failing layer before changing unrelated configuration. 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

• Record the exact QCLF version, affected Topic/live type, user role, and the five Scheduled Task states before changing anything.
• Check Status for entitlement/task health before treating a missing premium control as frontend corruption.
• Reproduce the problem with the smallest safe test rather than changing multiple settings at once.

Current QCLF Behavior

Step-by-Step Workflow

1. Record the exact failing action, QCLF version, URL/view, Topic type, user role, and current Base/Effective tier.
2. Open QCLF Status and Joomla Scheduled Tasks before changing configuration.
3. Reproduce the failure with the smallest safe test and determine whether the problem is access/ACL, entitlement, task/lifecycle, mail, browser/media, or data state.
4. Correct only the failing layer, then rerun the same test.
5. For live/notification problems, allow the relevant task cadence to run or execute the task intentionally when appropriate.
6. Collect non-secret evidence if support is still needed; never include passwords, keys, or private managed-service credentials.

Verify entitlement/tasks, structure/access, Discussion, Search/Following/Notifications, Live Ch

Verify entitlement/tasks, structure/access, Discussion, Search/Following/Notifications, Live Chat, paid live types, guest posting, email, mobile layouts, CSS, backup/update procedure 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

QCLF uses Joomla Scheduled Tasks for security-sensitive entitlement refresh and unattended live/notification maintenance; troubleshooting should identify the failing layer before changing unrelated configuration. 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 QCLF Production Go-Live Checklist, 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.

Verify the Result

• The task plugin is installed/enabled and each canonical task row exists without unintended duplicates.
• Entitlement Revalidation is not missing, unpublished, duplicated, or slower than hourly when premium access is expected.
• A representative Discussion, live session, archive, and email/notification workflow completes after maintenance.
• The installed version remains 1.1.27 and frontend JavaScript actions such as New Topic still function.

Common Mistakes to Avoid

• Treating a successful entitlement refresh that resolves Basic as a Scheduler failure; 1.1.26+ returns Scheduler OK for completed authoritative results.
• Reintroducing physical versioned forum-.js or hostlive-.js references instead of canonical forum.js/hostlive.js with query-string cache busting.
• Assuming low traffic automatically runs due Joomla tasks without an appropriate scheduler/cron strategy.
• Uninstalling to fix an ordinary update problem instead of diagnosing the exact failing layer.

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.