Rick Christopherson
09-10-2013, 5:42 PM
Just wondering if I am alone in noticing this.
The current setting for determining whether a thread/forum is considered read or unread is based on the time-out setting of the forum (somewhere between 30 and 45 minutes). When this timeout has been reached, the entire forum gets marked as read. That may not sound like a big deal, except it also removes some of the other features available for opening an unread thread, such as jumping to the newest post.
So for example, if you just started to visit the forum, but something came up and you had to answer an email or browse to another website, when you come back, the entire forum (and all subforums) will be marked as being read, and all unread thread features disabled.
This is controlled by a simple setting in the AdminCP under Settings/General/Thread/Forum Read Marking Type. Right now it is set to "Inactivity", but setting this to "Database (no automatic....)" will correct this without taking a noticeable hit on CPU or database process.
270646
270647
To minimize any database hit, you could set the Database Read Marking Limit to 1 day or 2 days. When this time period expires, all threads are considered read regardless whether the visitor has been to the forum or not.
270648
The current setting for determining whether a thread/forum is considered read or unread is based on the time-out setting of the forum (somewhere between 30 and 45 minutes). When this timeout has been reached, the entire forum gets marked as read. That may not sound like a big deal, except it also removes some of the other features available for opening an unread thread, such as jumping to the newest post.
So for example, if you just started to visit the forum, but something came up and you had to answer an email or browse to another website, when you come back, the entire forum (and all subforums) will be marked as being read, and all unread thread features disabled.
This is controlled by a simple setting in the AdminCP under Settings/General/Thread/Forum Read Marking Type. Right now it is set to "Inactivity", but setting this to "Database (no automatic....)" will correct this without taking a noticeable hit on CPU or database process.
270646
270647
To minimize any database hit, you could set the Database Read Marking Limit to 1 day or 2 days. When this time period expires, all threads are considered read regardless whether the visitor has been to the forum or not.
270648