patvdv
30th January 2006, 18:49
Hi all,
With the recent upgrade of the forum software, the mechanism to determine which posts are new for each user has also been changed or rather enhanced. I would like to hear the democrate vote off the members on this so please choose your favorite option after reading the explaination below.
The majority vote wins, even it means reverting the forum back to the previous mechanism. The poll will stay open until 31st March.
Theory:
The forum can operate in one of the following three manners:
Inactivity/Cookie Based - once a user has been inactive for a certain amount of time (ie 15 mins) 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.
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.
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.
Before the upgrade only the first option was available. Now we have switched to the third option which presents each user with an individually tailored list of which posts are new/unread, not just since your last visit but overall.
Practice:
Let's illustrate with an example of how what the main consequences are from switching to cookie-based to database-tracked tracking.
First, how would the screen of new posts look like before (using the View New Posts since Last Visit link):
2545
Then secondly, the next picture shows how a selection of new posts might look with database-tracking (using the All Unread Posts link):
2546
You will notice that the second screen shows the same information as the first but adds to that all other threads for which a user still has unread posts.
Questions:
Question: When using database tracking: how does the forum know when a thread should be marked as 'read'?
Answer: Either by the user reading all posts in the thread or by the user marking the thread as read using the Mark Forums As Read option. This marking can be done either on a global forum level (for all sub forums) or one individual forum.
2547 2548
Question: When using database tracking: will posts that I have not read be kept indefinatively in status 'unread'?
Answer: No. All your unread posts will be marked as 'read' 60 days after they have been published.
Related threads
UPGRADE: forum upgraded to vbulletin v3.5.3
What's New / Since ...
"View new posts" guts
New Threads: ## | New Posts: ##
New threads suggestion
Number of New Threads
With the recent upgrade of the forum software, the mechanism to determine which posts are new for each user has also been changed or rather enhanced. I would like to hear the democrate vote off the members on this so please choose your favorite option after reading the explaination below.
The majority vote wins, even it means reverting the forum back to the previous mechanism. The poll will stay open until 31st March.
Theory:
The forum can operate in one of the following three manners:
Inactivity/Cookie Based - once a user has been inactive for a certain amount of time (ie 15 mins) 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.
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.
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.
Before the upgrade only the first option was available. Now we have switched to the third option which presents each user with an individually tailored list of which posts are new/unread, not just since your last visit but overall.
Practice:
Let's illustrate with an example of how what the main consequences are from switching to cookie-based to database-tracked tracking.
First, how would the screen of new posts look like before (using the View New Posts since Last Visit link):
2545
Then secondly, the next picture shows how a selection of new posts might look with database-tracking (using the All Unread Posts link):
2546
You will notice that the second screen shows the same information as the first but adds to that all other threads for which a user still has unread posts.
Questions:
Question: When using database tracking: how does the forum know when a thread should be marked as 'read'?
Answer: Either by the user reading all posts in the thread or by the user marking the thread as read using the Mark Forums As Read option. This marking can be done either on a global forum level (for all sub forums) or one individual forum.
2547 2548
Question: When using database tracking: will posts that I have not read be kept indefinatively in status 'unread'?
Answer: No. All your unread posts will be marked as 'read' 60 days after they have been published.
Related threads
UPGRADE: forum upgraded to vbulletin v3.5.3
What's New / Since ...
"View new posts" guts
New Threads: ## | New Posts: ##
New threads suggestion
Number of New Threads