Show Thread Enhancements - Who has read a Thread

This modification is no longer available or supported.

This displays who has read a thread, and the time they last looked at it.

Hovering over a name will show when the member last viewed the thread, and (optionally) what IP address they viewed it from. Note that you can only view the ip addresses in the 'View-All' display.

There is also an option to allow a thread author to view who has read their thread when they are not in one of the allowed usergroups. The IP and number of days restrictions still apply.

The set/reset facility allows members to click on the 'set' link which then sets a personal 'cutoff' time - only showing who has read the thread after that time. The time can be reset as many times wanted, and also completely cleared again. When using this facility there is also a link to allow you to view a seperate list of all readers of the thread.

Warning: When using the set/reset option - there is only a limited capacity of entries per thread (several thousand) - therefore you should only allow this feature to be used by a limited number of people - typically Staff usergroups. Allowing all members to use it will probably slow down your forum and cause errors if more than about 3000 members set a date on one thread.

Note: You must have the "Show Users Browsing Threads" option set in your vbulletin options for this to display.

A cron job (optionally) allows the deletion of records from the whoread table that are over a certain age - this is provided for large forums where the number of table entries can start to reach a million or more after 12 months. The delete age is a setting in the ACP.

There are also settings for the following (in vBulletin Options > Who Has Read a Thread) ;

1. Turn the system on/off.
2. Restrict the display to certain usergroups
3. Restrict the IP display to certain usergroups.
4. Restrict the display to a set number of days.
5. Option to allow thread author to view who read information.
6. Option to turn on the who read cutoff date (reset) function
7. Restrict use of reset function to certain usergroups.
8. Option to set whoread data records to be cleaned out after xxx days.
9. Clicking on a user will display a page of their thread viewing history, most recent first.

Note: When using option 4 or the set/reset facility, the data is still kept beyond this limit, so they can be changed at any time.

Download the zip, extract the XML file and import using the vb Product Manager.

Version 3.7.006 has experimental support for TMS. If you have TMS installed then the existing automatic template update system will be disabled in favour of TMS. One effect of this is that when using TMS the requirement for "Show Users Browsing Threads" to be enabled is bypassed . This version will continue to work as before for those who do not use TMS.


History:

v3.7.001 : First Release for vb 3.7.
v3.7.002 : Added check for 'view others threads' permission.
v3.7.003 : Fix for cron_script hook changed in 3.7 Beta 4.
v3.7.004 : Bug fix for days limit when reset option is enabled.
v3.7.005 : Updated to remove potential $group variable name clash.
v3.7.006 : TMS Support added, this is currently experimental.
v3.7.007 : Threads read via the archive are now recorded. Minor permissions update as well.

[Paul M]

I would expect it to be something else using the same hook.

[gnavpott]

install

[aciurczak]

Here's another one, happening right now. User MSMC10 is on the thread as I'm typing this, he shows in the "currently viewing a thread", yet the entry in "who has read this thread" hasn't updated. 2nd screenshot shows that according to the standard "whos online" page, he's right on that thread and viewing an attachment from it...

Looking at my plug-in mgr for all the hooks, the only two products using that showthread_complete hook are "Guest Tracking" and "Who has read a thread". 3rd screenshot is of my admincp showing those two products using that hook. (they are the only ones on that screen with that hook).

[Paul M]

If you are viewing an attachment in a thread, you will show up in the "Currently Active Users Viewing This Thread" box, however, you will not be logged as viewing the thread by this mod. Maybe they are going direct to the attachment ?

Since you have the tracking mod installed as well, you can also check if that logged them in the thread.

[aciurczak]

The tracking mod does not log him as viewing that thread; the attachment is new, has a random ID that they wouldn't know; there is no way that they can be going to it directly without hitting the thread first.

The tracking mod in fact didn't log him at all. It logs back for 10 days for all other users, but he was here yesterday and it doesn't show anything at all. Here's a screenshot...

[Paul M]

Sorry but there is nothing I can tell you, if the hook is run, then the data will be recorded. I cannot explain why your forum is not running the hook, but clearly it hasnt, as two entirely seperate systems have not been updated.

[Paul M]

Actually, there is one other possibility (pointed out in another mod) which the update Ive just released covers. If a thread was read via the archive pages, then it would not be recorded, as this does not run showthread. The user would still show up in the browsing list.

[digicom]

Thanks Paul Apprciated :up:

[antialiasis]

Hello. I was trying to install this on my new board and am getting this database error during the installation:

Database error in vBulletin 3.7.1:

Invalid SQL:
INSERT DELAYED INTO whoread
(userid, threadid, dateline, ipaddress)
VALUES (74, 59, 1214242771, '');

MySQL Error : Table storage engine for 'whoread' doesn't have this option
Error Number : 1031
Request Date : Monday, June 23rd 2008 @ 07:41:07 PM
Error Date : Monday, June 23rd 2008 @ 07:41:07 PM

[Paul M]

Thats a mysql issue - your table does not seem to support the use of delayed inserts. You will have to edit the plugin to remove the DELAYED keyword.

(All that code does btw is copy existing vb read data into the new table on installation of the mod, you can just ignore the fact it failed and the mod will still work fine).