Display members who have recently read a thread

This modification is no longer available or supported.

If you have the new thread reading system enabled then this hack will use it to display anyone who has recently read a thread. The time limit is determined by your vb options thread marking limit.

You must be using the database thread marking system for this hack to work.


To install this hack, unzip the xml file and import it via the product manager.

The ACP settings are in vbulletin options > thread display options.


Upgrades:

To upgrade from version 2.18 or before, to version 2.21 onwards, you need to uninstall the product and remove the template code in SHOWTHREAD - then upload the new product. To upgrade from version 2.20 onwards, upload the new product with overwrite set to yes.


History:

v2.16 : Added ACP setting to turn the display on/off.
v2.17 : Added ACP setting to restrict which usergroups can view the display.
v2.18 : Added hover display to each username which shows the date/time of the last post (in the thread) at the time the member read it.
v2.19 : Not released.
v2.20 : Not released.
v2.21 : Removed the need to edit the SHOWTHREAD template.
v2.22 : Updated ACP view permission option to take into account secondary
v2.23 : Added 'nofollow' attribute to listed usernames.
v2.24 : Minor changes, no update necessary.

[microzott]

as more info: the link is shownig the date/time of the last post not the recently read date/time

my configuration step by step:

1) install every thing following paul instructions (template+product)
2) goto in the ACP/vBulletin Options/General settings and put a value for "Database Read Marking Limit" (I am using 30 days)
3) goto in the CP/vBulletin Options/General settings and flag "Database (no automatic forum marking)" in "Thread/Forum Read Marking Type"
4) goto in the CP/vBulletin Options/Thread Display Options (showthread) and flag "yes" in "Display who has Recently Read a Thread"
5) goto in the CP/vBulletin Options/Thread Display Options (showthread) and insert one or more usergroups in "Who has Recently Read a Thread Usergroups" (I have only the value 6 - administrators)

[aciurczak]

It's working exactly as designed. See post #66 just above. vbulletin doesn't store the time a member reads a thread. Paul made a great addition to his original hack by checking which posts a member read, and posting the time of the last read post when you hover over their name. Heck, even the text in your screenshot says "time of last read post", not "time they read the last post". This time is useful, because you can see which posts a member had read at the time they last visited the thread.

[Mastar]

Originally Posted by microzott

as more info: the link is shownig the date/time of the last post not the recently read date/time

my configuration step by step:

1) install every thing following paul instructions (template+product)
2) goto in the ACP/vBulletin Options/General settings and put a value for "Database Read Marking Limit" (I am using 30 days)
3) goto in the CP/vBulletin Options/General settings and flag "Database (no automatic forum marking)" in "Thread/Forum Read Marking Type"
4) goto in the CP/vBulletin Options/Thread Display Options (showthread) and flag "yes" in "Display who has Recently Read a Thread"
5) goto in the CP/vBulletin Options/Thread Display Options (showthread) and insert one or more usergroups in "Who has Recently Read a Thread Usergroups" (I have only the value 6 - administrators)

Thank you vry much for your assistance! And you are right the times don't match, its 10hrs 26 mins behind...

[Bounce]

/me installs

thanks paul

[microzott]

hi aciurczak,
I'm not sure if I have correctly understood...
...but the time displayed by the onmouseover is the date/time of the last post in that thread
...nothing related with the user, all users that have read that thread will display the exact time of the last post posted, is it correct?

see my post #89

[aciurczak]

No. Read post #66 again.

The mouseover time will show the time of the last post that that user read on the thread.

post 1 (10 AM)
post 2 (11 AM)
post 3 (12 noon)

user 1 visits the thread at 11:30, user 2 visits the thread at 12:30.

The mouseover time for user1 will be 11 AM, as that is the last post he saw. User2 will have a mouseover time of 12 noon.

"Time of last read post."

[Paul M]

Originally Posted by microzott

wher is it in the ACP? I don't remember and i can't' find it

changing all the if conditions in the product (false -> true in $show['whohasread'] = true now I can see the box, but still with no data
I confirm you that the admin user group is 6

is this one?

Originally Posted by microzott

now seems that is working

but I still have two issues to fix
1) find the correct parameter for "The amount of time in days to store the thread and forum read times. All threads or forums without posts in this many days will be considered read."

2) fix the "if" condition for the user groups

I have no idea what you have done, there is nothing needs editing or fixing. Simply install and make sure you have one of the database thread marking options selected (i.e. not the activity/cookie based option).

Originally Posted by microzott

but i think I have found a real bug:

No, you haven't read the notes properly. It is the "time of the last read post", that is the timestamp on the last post, at the point the member read the thread, not the time they read the thread. This means you can easily see what posts they have not yet seen/read.

[microzott]

Originally Posted by Paul M

I have no idea what you have done, there is nothing needs editing or fixing. Simply install and make sure you have one of the database thread marking options selected (i.e. not the activity/cookie based option).

No, you haven't read the notes properly. It is the "time of the last read post", that is the timestamp on the last post, at the point the member read the thread, not the time they read the thread. This means you can easily see what posts they have not yet seen/read.

ok, I am sorry
everything is fine and working, my mistake was the database thread marking option (I was using cookie based).

[Paul M]

Originally Posted by microzott

my mistake was the database thread marking option (I was using cookie based).

You're not the first, you won't be the last.

[ayaam]

good work , Thanks for update it to 3.5.1