Version: 1.2.1, by rob_daemon
Developer Last Online: Sep 2019
Version: 3.0.3
Rating:
Released: 08-27-2004
Last Update: 12-10-2004
Installs: 122
No support by the author.
Note: Development of this hack has stopped.
The built-in version is far superior to this hack and has better controls and permission checking. For those of you who will remain on 3.0.x, I will try to support this hack as best I can, but it won't be a top priority. If you plan on moving to 3.5, I hope this hack made your life a little bit easier while you waited .
Current Version: 1.2.1 (Wed Dec 11 15:26:30 PDT 2004)
What this is?
This hack will allow you and your moderators to do your job more effectively by allowing you to mass-moderate. You can perform the same action on multiple threads and posts without leaving the current page!
What is required?
In order to use this hack, you must have cookies and JavaScript enabled! If you don't, this hack will not work. (Note: there is no "alternative display" for people without JavaScript enabled).
How many changes?
Uploads: 2
File edits: 2
And template additions/edits
Support
I will provide all support here in this thread.
Bugs
I have thoroughly tested this hack with as many different combinations I could think of. But I probably have either over looked one or two, or just didn't think of some. If you find any odd behaviour, please let me know!
Changes Since
1.2.0
Fixed problems with merging threads
Enhancement to the merge thread screen
1.1.0
(Hopefully) resolved all JavaScript issues
Merge threads
Removed search results moderation ability (it was too much work to maintain and a user could bypass the protection if he knew how the hack operated)
Bug with not updating all user fields in post merge
Bug with checking for the wrong permissions when deleting a post
Template caching
Selection boxes only appear when a user is a moderator
1.0.0
Fixed search results
Added small announcement patch
Fixes For 1.2.1
The following fixes are in in the next version:
This hack seems to have added 5 queries to every forum page and the queries even show for regular users who are not mods\admins. Do these 5 queries increase load negatively?
Those queries are generated by can_moderate() and it only happens on showthread.php and forumdisplay.php. They're necessary because that's how it determines to see if the checkboxes should be placed on the page.
None of the queries should add too much load because they're all very simple SELECT statements.
sir,
i have used ur inline mod as mind giving problem but when i replace with the inlinemod.php given by u i get errors and when i replace it back with mine i get invalid path..i have attached inlinemod.php that was orignal from 3.6.8 patch maybe u can help me out on what i do so the inline moderation can work as of now both yours and the original is giving problems...
these are the error:
sticky/unsticky/move/unmove/delete has this error
print_standard_error(...)
is now redundant. Instead, use
standard_error(fetch_error(...))
close
Fatal error: Call to a member function query() on a non-object in /home/yahoocit/public_html/inlinemod.php on line 391
open
Fatal error: Call to a member function query() on a non-object in /home/yahoocit/public_html/inlinemod.php on line 412
sir,
i have used ur inline mod as mind giving problem but when i replace with the inlinemod.php given by u i get errors and when i replace it back with mine i get invalid path..i have attached inlinemod.php that was orignal from 3.6.8 patch maybe u can help me out on what i do so the inline moderation can work as of now both yours and the original is giving problems...
these are the error:
sticky/unsticky/move/unmove/delete has this error
print_standard_error(...)
is now redundant. Instead, use
standard_error(fetch_error(...))
close
Fatal error: Call to a member function query() on a non-object in /home/yahoocit/public_html/inlinemod.php on line 391
open
Fatal error: Call to a member function query() on a non-object in /home/yahoocit/public_html/inlinemod.php on line 412
You should NOT be using this with any other version than v3.0. That is what this was designed for and using it with future versions is a bad idea because it makes function calls that are incompatible with each other. This will not work at all with any other version than 3.0. Put back the version of the file that came with your version of vBulletin. If it is giving you problems, then contact Jelsoft for support. Furthermore, I no longer support this mod because vBulletin now includes this feature.