Threads being marked as unread after user makes reply.
 

So many issues with VB5. Wow. Kinda wish I stuck with 4 right about now.

The one that I'm concerned with right now though is the fact that when I post in a thread, the thread is marked as unread, even though I just read it, because of my own post.

Any idea why this would happen?

I have database marking on.

This is usually because there are still unread posts in the thread.

Hello, Mark B, we meet again. :P

No there are not. I'm not new to this, I've been running a vbulletin site for over 8 years. I know when things are not working correctly.

This is what is happening.

There are 3 posts in a thread. I go into that thread, reply to it, go back to the forum and it's still marked as unread. There are no new posts in that thread.

Sometimes it's just not being marked as read even if I'm not replying to it. Three posts.. ALL seen. Not marked as read.

:/

Could it be a slow DB or something?

--------------- Added [DATE]1421520844[/DATE] at [TIME]1421520844[/TIME] ---------------

Updated to patch 3, still the same problem.

And again my settings are set to...Database (automatic forum marking).

--------------- Added [DATE]1421521012[/DATE] at [TIME]1421521012[/TIME] ---------------

Also it looks like the thread IS being marked as read eventually. Just takes time.

--------------- Added [DATE]1421523868[/DATE] at [TIME]1421523868[/TIME] ---------------

Update:

I've also noticed it randomly marking threads as unread AFTER they've been marked as read and there is no new activity.

Double checked and not even a new comment, no new activity at all.

It happens on vB.com to me as well, just another unintended feature in the product.

Happens at vb.com all the time. In the feedback forum there's a thread with 2 pages which I have opened like two dozen times, and still it shows unread. Mark channel read doesn't work either. "Unintended feature" - ozzy, that's simply great. I bet IB will use that for their product spinning in the future.

Yeah I have always liked the phrase, "unintended feature", it is a nice way to describe a bug. :)

<a href="http://tracker.vbulletin.com/browse/VBV-4564" target="_blank">http://tracker.vbulletin.com/browse/VBV-4564</a>

If the ajax call doesn't finish properly, it doesn't get marked as read.

This one has been on my most annoying list for awhile. I looked at it once, and if I remember correctly is a data-read-time issue. Now I won't be able to ignore after posting this.

Are you running 5.1.4 PL3 ?

PL3 comes this weekend. Why? is this fixed in the patch?