Configure Category Auto-Lock After Inactivity

Set or disable automatic Topic locking after inactivity and distinguish it from moderator manual locking.

This guide follows the accepted QC Live Forum 1.1.27 implementation and applies to All plans; administrator. QCLF structure is the foundation for content and live features: Sections group Categories, Categories own Topics, and access/capability rules decide what each Joomla user can see and do. 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

• Map the intended public/member/moderator Joomla groups and view levels before creating a large Section/Category tree.
• Decide which forum capabilities should be inherited globally and which genuinely need Section or Category overrides.
• Use a non-Super-User account in the exact production group when testing permissions.

Current QCLF Behavior

Step-by-Step Workflow

1. Open Administrator → Components → QC Live Forum → Sections & Categories.
2. Select the relevant Section or Category, or create a new one if the task calls for it.
3. Set publication, Joomla access level, ordering, and feature inheritance before adding narrower overrides.
4. Configure QCLF action rules or moderator groups only where the default/inherited behavior is insufficient.
5. Save, then test from the frontend with the exact Joomla group that should be allowed.
6. Repeat the test with a user who should be denied; visibility and action authorization should both match the intended design.

Set or disable automatic Topic locking after inactivity and distinguish it from moderator manua

Set or disable automatic Topic locking after inactivity and distinguish it from moderator manual locking 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 structure is the foundation for content and live features: Sections group Categories, Categories own Topics, and access/capability rules decide what each Joomla user can see and do. 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 Configure Category Auto-Lock After Inactivity, 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 intended user can see the Section and Category but an unauthorized test user cannot.
• Create/reply/live capabilities match the Category ACL and inherited feature settings.
• Global and Category moderator groups have the intended scope without unnecessary Joomla backend access.
• Reordering does not change Section/Category identity or unexpectedly change downgrade entitlement order.

Common Mistakes to Avoid

• Relying on menu access alone instead of Section/Category access and QCLF action rules.
• Adding overrides everywhere when inheritance already provides the desired behavior.
• Testing permissions only as Super User.
• Deleting a Category before resolving active Topics, drafts, restrictions, or related retained data.

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.