Use the Deleted Topics Recovery Expander

Explain current moderator-only Category recovery access, deleted Topic counts, and why ordinary users do not see the control.

This guide follows the accepted QC Live Forum 1.1.27 implementation and applies to All plans; effective moderators. QCLF moderation is frontend-first and scope-aware, allowing trusted moderators to handle reports, users, content, live sessions, and guest submissions without turning them into Joomla backend administrators. 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

• Use the frontend Moderation workspace with an account that has actual moderation scope; backend component access alone is not enough.
• Decide whether the action should affect one Category, one Section, or the forum globally before applying a user sanction.
• If guest posting is enabled, configure Joomla CAPTCHA first and test the pending-approval workflow before opening it publicly.

Current QCLF Behavior

Step-by-Step Workflow

1. Sign in as the real moderator role and open Browse → Moderation.
2. Choose the relevant subtab—Reports, Users, Content, Live, or History—rather than using Joomla Administrator for ordinary moderation.
3. Open the target report, user, Topic, Message, guest submission, or live session and confirm your moderation scope.
4. Apply the narrowest action that solves the problem: resolve/dismiss, edit/reject/approve, lock, move, restore, sanction, split, merge, or purge when explicitly required.
5. Reload the affected frontend area with both moderator and member test accounts to verify visibility and restrictions.
6. Review moderation history when the action should be auditable.

current moderator-only Category recovery access, deleted Topic counts, and why ordinary users d

Explain current moderator-only Category recovery access, deleted Topic counts, and why ordinary users do not see the control 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 moderation is frontend-first and scope-aware, allowing trusted moderators to handle reports, users, content, live sessions, and guest submissions without turning them into Joomla backend administrators. 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 Use the Deleted Topics Recovery Expander, 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 action appears only to moderators with scope over the affected content/user.
• Pending guest content remains out of public lists/search/counts/notifications until approved.
• A sanction blocks only the intended activities and scope.
• Move/merge/split/recovery actions preserve the surviving Topic/message history and intended redirects/references.

Common Mistakes to Avoid

• Granting Joomla backend access just to perform ordinary forum moderation.
• Enabling guest posting without CAPTCHA and sensible posting/link/duplicate controls.
• Assuming every explicit Category ACL row makes someone a moderator.
• Permanently purging soft-deleted content before the retention/recovery decision is complete.

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.