Version: 1.01, by cheesegrits
Developer Last Online: Nov 2011
Category: New Posting Features -
Version: 3.7.0 Beta 4
Rating:
Released: 02-22-2008
Last Update: 02-22-2008
Installs: 38
Uses Plugins
Re-useable Code Translations Is in Beta Stage
No support by the author.
WARNING - this mod is currently in Beta test! I've done as much testing as I can on a small development board, but have not run it on anything like a busy board. While there is no possibility of this mod damaging your board, there may be some unforeseen issues. Please post here with any questions, concerns, bug reports or suggestions.
Description
When this product is enabled, users are warned when responding to a thread if that thread has been updated since their "last visit". If they are using "Post Reply" they are bounced to a preview page, with a warning, an updated thread summary, and they have to re-submit their response. If posting from Quick Reply, they are warned, but the thread display is not updated (still working on that!), so the default warning suggests they "Go Advanced" and check the new thread display (although they may simply resubmit and it will go through).
Settings
The product has three AdminCP settings (in the Check Post section of the main vBulletin Settings).
Check Post Enabled: you can turn check post on and off.
Sound Effects: by default, when a post is aborted because of a thread update, a sound effect is played to get the users attention. You can disable this with an ACP option. SFX are only used on the Post Reply bounce, not with Quick Reply.
Forums to Exclude: a comma separated list of forum ID's not to apply Check Post to.
You may also customize the warning message by editing the checkpost_warning template, and/or the phrases referenced by the template. If you want a different sound effect, change the URL in the template.
Installation
Install the product XML.
Uninstallation
Uninstall the product XML.
To Do
1. Add a 'Forums to Exclude" ACP setting. I suspect that this mod could become unwieldy in a very busy forum. DONE.
2. Add a "Usergroups to Exlcude" ACP setting. Admins and Moderators may not care to be warned about thread updates.
3. Find a way to update the postbits on an AJAX Quick Reply. A Catch 22 in the way newreply.php works make it impossible to both update the postbit, AND abort the post and return a warning. The only way I can see of doing this involves duplicating much of what newreply.php does to rebuild the postbits. I'll continue to work on this!
This could come in handy for those members that reply to a post much slower than other members, in other words this can prevent many users from saying the same thing.
I like the concept, but I would like it MORE if I could select to activate it ONLY in a specified forum instead of board wide.
I'll keep an eye on this and will most likely use it when you get your "forum to exclude" function to work.
To be honest, I got the idea from SMF (Simple Machines Forums), which I hate, but it does have this one feature I like that vB doesn't have.
As for the Beta testing status, don't be too scared. I haven't had any bug reports yet, and the mod is very simple. It's either going to work on your forum or it isn't. If it doesn't, just turn it off, let me know and I'll work out what the problem is. It won't damage your board in any way. The only database write it does is to update the 'last activity' date for the user in the session table when they are using Quick Reply (for some reason, vB doesn't do it when using Quick Reply).
Good point. If the posts are made in exactly the same second, Check Post won't trigger. I guess I could change that so it tests for "less than or equal to" instead of "less than". I'll probably do that in the next release. Meanwhile if you want to change that behaviour, edit the newreply_post_start hook, and in the 'if' statement:
PHP Code:
if (!in_array($threadinfo['forumid'],$checkpost_forum_exclude) and $vbulletin->userinfo['userid'] and $vbulletin->options['checkpost_enabled'] and $vbulletin->userinfo['lastactivity'] < $threadinfo['lastpost'])
That should be commented out, is it not? When I'm debugging, I run the code as required files, so I can put breakpoints in it. Can't do that with pure eval'ed code in plugins. If it isn't commented out, it should be, I'll have a look.