Version: 2.0, by Abe1
Developer Last Online: Jun 2010
Category: Moderators Functions -
Version: 3.7.x
Rating:
Released: 03-04-2008
Last Update: 03-04-2008
Installs: 1468
DB Changes Uses Plugins
Additional Files
No support by the author.
Force Users to Read a Thread 2.0
About this hack:
This hack allows you to set a thread as 'must read' by your members. Right now, if you make a post and want all your members to read it, you have no way of enforcing it. This hack will give an error message similar to the one you get when you need to change you password, saying that the admins want you to read a certain thread before they continue using the forum.
Once a user reads a thread, they wont be bugged to read it again.
You can set all usergroups or just certain onces that must read a thread.
You can set to site wide or just some forums.
Option to Force Guests
This hack added one query to every page on your forum a member goes to.
Files edited: 0
Templates edited: 0
Files to upload: 2 (1 via ACP, 2 via FTP)
Time to install: 1 minute
Updates:
Version 2.0 (03/05/08):
First Release of this Hack for vb3.7
MAJOR update. Hack totally re-writen. You must uninstall old version before upgrading.
Fixed just about all bugs. (like if you delete a thread...)
No more template edit. Everything done in ACP.
Permissions for by who ever has ACP access with threads and posts
Force Guests to read a thread now.
Works for BOTH vb3.6 AND vb3.7
Please post your comments or suggestions for this hack. I read ALL posts.
MAKE SURE YOU CLICK INSTALL! You will get an email when a new version is released.
gr8 stuff but most of the time this doesn't work right for my members or my self
getting 404 error msg , using v 3.8.0
anyone know how to fix this, plz let me know.....thanks
Abe1, lack of indexes seriously f@#kup mysql server when you have "forced" threads.
Code:
ALTER TABLE `thread` ADD INDEX `force_read` ( `force_read` , `force_read_expire_date` )
Test your mods with slow queries log option "log_queries_not_using_indexes"
It's also possible to optimize queries. Instead of checking forced threads at each page loads, status can be cached in sessions table. For example, to check only once per hour.
Abe1, lack of indexes seriously f@#kup mysql server when you have "forced" threads.
Code:
ALTER TABLE `thread` ADD INDEX `force_read` ( `force_read` , `force_read_expire_date` )
Test your mods with slow queries log option "log_queries_not_using_indexes"
It's also possible to optimize queries. Instead of checking forced threads at each page loads, status can be cached in sessions table. For example, to check only once per hour.
I believe this is exactly what I pointed out in this post.
Question is why does it seem to only affect some of us?
I guess, that affects everybody . There are no reasons to guess - just make your sql-server log queries without indexes, and you will see almost all suspitious hacks.
Add that index and you'll be very surprised with server load. Don't forget to compare results
I like Abe1's modifications and his coding style. But I'm very surprised with DB design "holes". Have published fixes for Thanks & Groan hacks in apropriate threads.