There appear to be various circumstances where posts become New Post
, and threads show with unread posts, where they may not be.
Is there a simple method where a logged in user can 'Mark All Posts Read'?
There appear to be various circumstances where posts become New Post
, and threads show with unread posts, where they may not be.
Is there a simple method where a logged in user can 'Mark All Posts Read'?
There isn't, but I agree its useful and I'll put it on my roadmap for one of future releases.
I've had a look in at dprevived. They appear to be doing good work with .css and plugins (I assume).
The rate at which posts appear would make "mark as read" quite handy there.
Don’t worry, this is still on my list. Its just that notifications have much bigger priority.
Marking whole site as read, even selected categories is relatively achievable with current read tracker so here’s cherry on top.
There’s also an issue with islands of unread content, they have „read all posts” button on thread view to fix that, but proper fix is changing read tracker algorithm in Misago to don’t be post accurate. Its ironic how forums went from „we do per thread accuracy because performance for posts accuracy is terrible” to „we do percpost accuracy because that helps people spot edits and approved recently hidden content” to „people don’t care about thread content they skipped so don’t flag it as unread”.
"Mark all as read" could be a button on threads lists and categories list. There would be separate one for threads and for private threads. Pressing button would mark all threads/categories as read, but would also make all notifications associated with categories as read.
Making this button per category is tricky as it would require tracking per-category read cutoff (either separate JSON field on user model or separate table), and would require category tree traversal to find out which read cutoff to use per category.
Making this button per thread is even worse because currently Misago is doing per-post accurate read tracking, so one would have to either quickly implement per-thread read tracking (which is impossible) or delay it until per-thread read tracking is implemented in future. But once per-thread read tracker is in, it would be easy as pie to implement "Mark thread as read" option.
Mark all threads/private threads as read: possible soon(ish).
Mark category as read: in future, after some cleanups to caching and permissions system.
Mark thread as read: in future, when read tracker is made thread accurate.
I am moving this into the scope of Misago 0.40, because it doesn't make much sense to me to have a per-post accurate read tracking with redone thread views.
The recent changes to notifications handling has made the management of unread threads much easier for the user. Perfectly reasonable to move things on to a sensible schedule for you. I still think there's a value to this.
This feature was implemented as a part of new reads tracker and will ship in Misago 0.40