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!
I haven't been able to duplicate zaimbat's problem, unfortunately.
I was wandering.. is it possible the problem is caused by LAG? Maybe the post is .. "sent" to the forum .. then lag.. lag.. then your script check for new posts and find out a new post, which is mine. Is there any improvement to exclude this possible bug? Maybe lifting "up" the "is there a new reply?".
Other question: can I see the preview of the new posts? this could help me even for my problem!