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: as of v3.34 you can only view the ip addresses in the 'View-All' display).

There is now 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.

A new time set/reset facility has been added. Members allowed to use this facility can click on the 'set' link and it will set a personal 'cutoff' time - only showing who has read the thread after that time. The time can be reset as many times as you want, 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.

A cron job has now been added that can (optionally) delete 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.

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.


There are 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.

New in v3.28

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.

New in v3.39

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.


History:

v3.20 : First Release for vb 3.6, a few code changes.
v3.21 : Dependancies updated for 3.6.0 Gold.
v3.22 : Updated for Version Checking.
v3.23 : Internal Development version.
v3.24 : Internal Development version.
v3.25 : Internal Development version.
v3.26 : Internal Development version.
v3.27 : Private release.
v3.28 : Public release of new features.
v3.29 : Fixed bug in clean-up, the setting was hours, not days.
v3.30 : Added options to disable/change auto template insert (not released).
v3.31 : Internal Code Changes, Settings Group renamed.
v3.32 : Minor template change.
v3.33 : SQL Changes to use slave.
v3.34 : Added new template for username display code, made 'View-All' always available.
v3.35 : Added last post marker to 'View-All' display.
v3.36 : Fix uncached templates.
v3.37 : Fixed missing date/time display when 'set' function is used.
v3.38 : Moved auto-template options to mods main settings group.
v3.39 : Version infomation added, display of user thread reading activity added.
v3.40 : Bugfix : Correct bugs reported in posts #308 & #318.
v3.41 : Minor changes to install code only.

[JenniferK]

Please help

I am finally preparing to upgrade to 3.7. I am working on my test board and when I uninstall this mod, I get this:

Database error in vBulletin 3.6.1:

Invalid SQL:

SELECT threadid
FROM whoread
WHERE userid = 1 AND threadid IN (83485,81768,57213,52924,52805,50681,50673,48091,3 8735,36959,36878,36741,30566,26797,11947,10180,749 7,6689,6226,5618,3630,3561);

MySQL Error : Table 'huntley_test.whoread' doesn't exist



I guess it didn't uninstall completely and now I don't know how to fix it. I also timed out in the ACP for my test board and can no longer log in because of the database error. Can someone please help me?

[Paul M]

How exactly did you uninstall it ?

[JenniferK]

In the ACP, under Manage Products, I went to the mod and clicked on uninstall.

[Paul M]

I dont see how you can get that error then. Maybe you have more than one version installed ?

[perfphysio]

I have been asking for a long time if someone could intergrate a way to email all those people who have read the thread. Perhaps to integrate it with the email functionality within admin.

Anyone with any ideas on that? Afterall normally once you find a group interested in a thread you wish to perhaps contact them?

[JenniferK]

Originally Posted by Paul M

I dont see how you can get that error then. Maybe you have more than one version installed ?

No, I never had any issues with this mod - it has always worked great. Never needed to reinstall. The site I was using it on was not one I tinkered with once it was first put up (which is why it's still running such an old version). It's still the original install I did around 2 years ago.

I plan to use the updated one once I upgrade. But I am unable to even get into my ACP (luckily it is just for my test board right now). I am by no means a techie, so I am totally lost as to what to do.

[Paul M]

I suggest you re-install it, then uninstall it again, and see what that does.

[JenniferK]

That was actually my thought, but I can't get into my ACP!

[JenniferK]

Anyone have any ideas? I am now a full day behind because I can't access my ACP to do anything.

[JenniferK]

I really hate to be a nag, but this is really a problem. I know it is just my test board, but I need to finish testing everything before I can go ahead with the upgrade on my live board (and obviously things like this are the reason for using a test board). I only have so much time alotted to do this all in, so I really need to get going. Any help anyone could give me would be greatly appreciated. There must be some way to fix this - I just have no idea how.