Sorry about that; demo accounts can now see the thread readers display at the bottom. I get your point; this hack is just reading what's in the db, not controlling what's in the db. I guess then this needs to be submitted to vb.com as buggy/unexpected behavior with their thread marking system.
No matter how many times I go back to an older thread, with a new user account that has never seen that thread, or a veteran user account even after that 60 day (or whatever you have it set to) window is over, it will not mark as read unless a new post is put into that thread.
Couple things could be causing this, but the most likely now that I think about it is that the older threads/posts may have been created when my forum was using 3.0.X, and I have since upgraded (like many of us) to the 3.5.X series.
|