Marking forums read
We were using Option 1 below. I have updated to Option 2. This should fix your problem. Just a warning, if processing times start to cause problems, we may need to go back to 1. I hope not though.
Here's the info:
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.
Here's the info:
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.
Thanks! My initial testing has confirmed that this option you selected takes care of the main problem, now I can step away either by logging out or not logging out and the forums I have read are still marked read and the ones I haven't aren't. While option 3 would take care of the other little annoyance option 2 is good enough for me. Thanks again!
I'm not a fan, It leaves me with 20 pages of "new posts" even though they are not new.
This sucks because I cant tell how long its going to take me to read through the new posts. Its going to get old if I have to plan on reading 20 pages of posts everytime, when in actuality, there are only 3 pages...
This sucks because I cant tell how long its going to take me to read through the new posts. Its going to get old if I have to plan on reading 20 pages of posts everytime, when in actuality, there are only 3 pages...
You can also go up to Quick Links and mark all forums read. That way you can start afresh with the posts that are made form that point forward.
However, I am interested in your feedback, so please let me know what you think...
However, I am interested in your feedback, so please let me know what you think...
If you go into a sub-forum, lets say General Discussion. You should see a drop down menu that says Forum Tools. One option is to mark that Forum as read.
I just find it most annoying that once you read a thread that it dissapears off of your new posts page, and that if you don't mark forms read, they will show up after I come back to the site after a few hours on my new posts page even though I chose not to read them.


