Fixed "Mark Read" issues

Affected version
v2.1.8 Patch 2

Harpers Tate

Well-known member
Read vs. unread is signified by regular vs. bold font attribute in the forum listing. This is about this font attribute (bold vs. regular).

Issue 1:
Read vs. unread is signified by regular vs. bold font attribute in the forum listing. This is about this font attribute (bold vs. regular).
There is a forum (parent node) with a sub-forum. And that sub-forum has a further sub-forum below it. (Thus three - or more - layers).
If you Mark Forum Read on the parent node, the read indication carries through to the sub-forum, but not to the sub-sub-forum. (i.e. it only goes down one level, never more).

Issue 2:
All of the threads in two forums, and the forums themselves are marked as read.
A new post or thread occurs in one forum. Thus the forum and the thread go "unread".
Read the thread; post in it, even. It goes "read".
Move the thread to the other forum.
The second forum goes unread, even though all its contents are read.
 

Chris D

XenForo developer
Staff member
Issue 1:
Read vs. unread is signified by regular vs. bold font attribute in the forum listing. This is about this font attribute (bold vs. regular).
There is a forum (parent node) with a sub-forum. And that sub-forum has a further sub-forum below it. (Thus three - or more - layers).
If you Mark Forum Read on the parent node, the read indication carries through to the sub-forum, but not to the sub-sub-forum. (i.e. it only goes down one level, never more).
This is a bug that will be fixed in the next release.


Issue 2:
All of the threads in two forums, and the forums themselves are marked as read.
A new post or thread occurs in one forum. Thus the forum and the thread go "unread".
Read the thread; post in it, even. It goes "read".
Move the thread to the other forum.
The second forum goes unread, even though all its contents are read.
This one is a design issue, essentially. We have no plans to change it as, even if it were possible to, it would require updating a significant amount of individual user read records which would likely take far too long and quickly become irrelevant by the time the user has visited the forum again.

Some more detail contained here:
 

XF Bug Bot

XenForo bug fixer bot
Staff member
Thank you for reporting this issue, it has now been resolved. We are aiming to include any changes that have been made in a future XF release (2.1.10).

Change log:
Ensure we mark all forum descendants read when marking a forum read - not just its children.
There may be a delay before changes are rolled out to the XenForo Community.
 
Top