It might be worth looking into a way for the userbase of a community to click a button (maybe from the notification viewer) to allow users to clear their notification history for self-maintenance.
All the button would need to do is clear out the notifications for the current logged-in user within the database.
Wow.... is that really how the notification table is structured...?
There's no "flag" in place to mark the notification as viewed per user_id?
That's kinda scary from a technical standpoint, this gives the users zero control over their notifications as they are provided with two options, either have your notification view is flooded with no way of cleaning up old notifications OR just never getting the notifications to begin with.
This in turn forces the administrator to play a card that displeases most of their userbase when they decide to clear out old notifications, while the handful of people that would love an archive suddenly find their notifications missing.
Was this not thought of when the notification framework was made?
Hello @Scotti !
No, there is not a special procedure for it. But we have the old notifications cleaner in the DB prunning.
L
It might be worth looking into a way for the userbase of a community to click a button (maybe from the notification viewer) to allow users to clear their notification history for self-maintenance.
All the button would need to do is clear out the notifications for the current logged-in user within the database.
The notifications records are made to be shown not only for the one recipient, so it's not possible to have similar button.
L
Wow.... is that really how the notification table is structured...?
There's no "flag" in place to mark the notification as viewed per user_id?
That's kinda scary from a technical standpoint, this gives the users zero control over their notifications as they are provided with two options, either have your notification view is flooded with no way of cleaning up old notifications OR just never getting the notifications to begin with.
This in turn forces the administrator to play a card that displeases most of their userbase when they decide to clear out old notifications, while the handful of people that would love an archive suddenly find their notifications missing.
Was this not thought of when the notification framework was made?