Manage On-Site Notification History

Mark individual/all notifications read, delete entries, clear display history, and understand that history cleanup does not resend old email.

This guide follows the accepted QC Live Forum 1.1.27 implementation and applies to All plans; signed-in members. Search and personalized activity views are built around the same access rules as the forum itself, so useful discovery should never become a privacy side channel. 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

• Sign in when testing personalized lists, Following, Unread, delivery preferences, or notification history.
• Use a second account with different Section/Category access to verify that private content does not leak through search or notifications.
• Separate the follow relationship from delivery preferences: following an item and choosing email/on-site delivery are related but distinct.

Current QCLF Behavior

Step-by-Step Workflow

1. Sign in with the member account whose personalized state you want to change or inspect.
2. Open the relevant Browse view: Following, Follow Delivery, Unread, My Topics, Notifications, or Starting Soon.
3. Perform the specific follow, delivery, read-state, or notification action described by this guide.
4. Reload the view and confirm the stored relationship/state changed without altering unrelated preferences.
5. Trigger one safe test activity from another account when you need to verify delivery or unread behavior end to end.

Mark individual/all notifications read, delete entries, clear display history, and understand t

Mark individual/all notifications read, delete entries, clear display history, and understand that history cleanup does not resend old email 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.

For live features, separate the durable Topic from the temporary live-session state. Scheduling, playback/media state, participant controls, end/grace handling, and archive conversion are lifecycle concerns; the Topic URL and permanent archived conversation are the durable forum record.

How This Fits into QC Live Forum

Search and personalized activity views are built around the same access rules as the forum itself, so useful discovery should never become a privacy side channel. 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 Manage On-Site Notification History, 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

• Search returns the intended accessible match and does not reveal the same content to an unauthorized account.
• Unread, Following, and My Topics update after the relevant user action.
• Follow Delivery reflects the saved Topic/Category follow and selected email/on-site options.
• Live reminder timing changes correctly after schedule changes or cancellation.

Common Mistakes to Avoid

• Assuming following automatically means every delivery channel is enabled.
• Testing privacy only with an Administrator account.
• Treating notification history deletion as a request to resend prior email.
• Using search result counts to infer inaccessible forum content.

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.