I had SkipGuy1 (née ScrollGuy1) use a topics replies columns “jump button” to go directly to the last post of a couple of never before entered 38 posts topics.
His post count in the Users page went up 76 posts, his profile post count went up by 2
Chasing down the elusive posts read value was an adventure.
The Users page gets the posts_read value from directory_items
directory_items gets the value from user_visits
The value in users_visits is set from user.rb
user.rb gets the value from topic_users
topic_users has “last read” and “highest seen”. IMHO the code does a great job of keeping track of what is “unread” for me, a great job of remembering where I left off reading in a topic, and a great job of sending me Notifications.
I’m guessing that when posts_read was hooked to this table it was assumed, consciously or otherwise, that members would enter a topic at the beginning and progress sequentially through the posts. That is, “jumps” were unforeseen.
A members profile on the other hand gets the posts_read value from user_stats
I’m thinking it might be a relatively easy fix to have the Users page also use the user_stats table. But I haven’t looked into it enough or tried any code changes yet to know for sure.