Unread marking

[twistsol]

Just this one that would not reset after reading. I had a couple of others, but they reset after reloading the site from the bookmark. I suspect the server had temporary database issues.

It would appear that if the last post is a comment rather than a reply, the system has a difficult time marking the item as read. I've opened a bug report with vBulletin.

[LCHIEN]

AFAIK, "Unread" tags is working properly for me.

[Jim Frye]

I haven't seen it happen since. I'm going to chalk it up to a server glitch. I've seen database update timing issues on other sites served by mult-customer applications.

[LCHIEN]

Whats the difference between the unread tag and the thread title in bold?

[LCHIEN]

OK I see an instance where this is perhaps not working intuitively.
The comment is new and flagged as unread, but reading the thread does not clear the "unread" flag. or the BOLDing of the title that also indicates unread. It's #12.2 the 2nd comment to the 12th of 15 total posts.

[Jim Frye]

OK I see an instance where this is perhaps not working intuitively.
The comment is new and flagged as unread, but reading the thread does not clear the "unread" flag. or the BOLDing of the title that also indicates unread. It's #12.2 the 2nd comment to the 12th of 15 total posts.

I'm seeing same issue with the same post, repeatedly, so it's not a timing or server busy issue. The other "unread" flagged thread (this one) reset properly. Must be a database management issue with the new version of software.

[twistsol]

vBulletin has confirmed this is a bug introduced in verion 6.08 when the rewrote the read marking system. This bug has only two votes and is not scheduled to be worked on yet.