This afternoon there was a DB problem and I got a vBull message to that effect. Even though I couldn't access the forums I still had the visit logged so it reset the last visit/all posts read time. Also, and this is common in most vBull forums, is that if I am idle for a period of time it resets the visit time and posts read. Cant that be set to be based on a session??

Hello...

Sorry to say nothing really can be done about the issue for it is all based on last visit time to the site and has a timer for a reset at 20 mins.

I am not sure if the new version of Vb addresses the issue. But I guess we will find out when we get to that point.

And I thought this thread was going to be about how you go though withdraw. ;)

It is a flaw or bug in vBulletin in that it resets things related to threads. It's been this way for many versions of vBulletin and certainly not limited to this site. I will go to my 'user cp' page and see (4) updated threads. I might only read one and have to leave. When I come back, I expect the other (3) to still remain there as being not visited, but too often, they're gone.

Related to this, and again it's not an AVS issue, the "last post" button is useless. I want it to take me to the newest post since I last visited the thread. In an active thread, you might have to back-track pages to start up where you left off.

Right, like I said, it is all based on the cookie timer and being on the site. Nothing I can really do about it as mentioned and as you seem to know. :)

If you agree that it doesn't work the way one would think it should or like it too, can you report it to vBulletin ?? I think site operators (customers) would have a bit more weight than users would.

Show the vBulletin people a user's "post list" page from DSL Reports. Granted, that's home-grown forum software, but I can be the 2nd poster in a thread and not come back for days. When I do, if that thread is now (10) pages long, I can click a link that takes me to the 3rd post in that thread -- the most recent one since I last visited the thread -- instead of taking me to the end of page 10.

As mentioned....I am not sure if this has been corrected in the current version, but it has been a long known issue and does not affect 95% of the sites that run Vb for they are not large enough to have such an issue. (Come in, read, leave for the site is small.)

Last night during the Google attack, the cookie timer did not time out.