Quote:
Originally Posted by tunaman3000
I
So this is a change you made recently? I am viewing the list of threads and it still is marked as unread. :/
Then you're doing something wrong, not what I said.
Let's say there's one unread post in one thread in a whole forum. You then read that post, browse back to the list of threads (just clicking back won't refresh / mark the database), and the forum will be marked as read.
If it's not doing that go ahead and manually mark the forum as read by double clicking on the little icon to the left of it in the forum list. That should clear any glitches. The reason for the change:
Quote:
Originally Posted by vB options
Thread/Forum Read Marking Type
This option controls how threads and forums are marked as read.
1. Inactivity/Cookie Based - once a user has been inactive for a certain amount of time (the value of the session timeout option) all threads and forums are considered read. Individual threads are marked as read within a session via cookies.
This option is how all versions of vBulletin before 3.5 functioned.
2. Database (no automatic forum marking) - this option uses the database to store thread and forum read times. This allows accurate read markers to be kept indefinitely. However, in order for a forum to be marked read when all threads are read, the user must view the list of threads for that forum.
This option is more space and processor intensive than inactivity-based marking.
3. Database (automatic forum marking) - this option is the same as a previous option, but forums are automatically marked as read when the last new thread is read.
This is the most usable option for end users, but most processor intensive.
Also
http://www.vbulletin.org/forum/showthread.php?t=172692
The difference between 2 and 3 is significant for the server, yet hopefully minor for users here. Since 2+2 is so busy (you almost always have at least 1 unread post in a forum anyway), my thinking was the difference should barely even register to most people.