View Single Post
  #5 (permalink)  
Old 03-26-2009, 10:37 AM
Otto's Avatar
Otto Otto is offline
Join Date: Nov 2008
Location: Atlanta, GA
Posts: 2,033
Blog Entries: 14

Navi, see below. We utilize the third option, which was new to vBulletin 3.5 and the best option available (as you can see). This removes the unreliable nature of cookies and end-user system issues from the per-user post/thread tracking. This makes the forum seem more like an email interface rather than the legacy forum systems. Most commercial non-vBulletin systems had moved to this method a while ago, and this is now the recommended defacto for tracking by vBulletin.

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.
BCSA (4.1, 5.0) | BCSD (4.1, 5.0)

The views expressed by me on are my own and do not necessarily reflect the views of my employer.
Reply With Quote