Hooks Manager v2
 

Well as the vBulletin are request extra hook locations, i find it very hard that they would be able to forfill everyones request, because if they did the php files would mostly contain hook calls, so to ease the pain of adding you're own hooks manually, i have created this addon, to add/edit/delete your own hooks using the acp! :)

Features:

• Adding A Custom Hook
  • Hook Category
  • Hook Name
  • Choose ANY PHP file in your forums directory to place the hook (including sub-fodlers)
  • Insert a line of PHP from the specified file to designate where the hook will be placed
  • Choose to locate the hook above or below the specified line of PHP
  • Will automatically modify your PHP file AND vbulletin_hooks.xml for you.
  • View file contents : Will automatically show the contents of the PHP file, so you can choose where to place the hook.
• Modifying A Custom Hook
  • Change any details you inputted while creating the custom hook
  • Any plugins assigned to it will be moved to the edited version (if the hook name is changed)
• Deleting A Custom Hook
  • Removes all file edits for that specific hook
  • Deletes all plugins assigned to that hook location
• Repairing All Custom Hooks
  • Repairs all custom hooks : This is designed to keep your custom hooks intact, if you accidently overwrite any file with a custom hook or vbulletin_hooks.xml, or if you've just upgraded your vBulletin forum, the repair function will re-insert ALL custom hooks back onto your system, with no manual file modifications required.
• Export Custom Hook Locations To Auto Installer
  • The custom hooks exporter is aimed at developers, and will automatically create an install file for people to use and run on there server, the intention is that you export custom hook locations for people to install so that your own modification runs off these hook locations. Please ensure that you notify users installing any modifications you provide with a custom hooks export installer to run the custom hooks installer first before proceeding to import any plugins!.
  • Installer Includes: Installer/Uninstaller/Repairer for all custom hook locations exported inside it.

File edits: 3 (admincp/plugin.php & includes/xml/cpnav_vbulletin.xml)
Requirements: CHMOD all php files in your forums directory (including sub folders) to 0666, and includes/xml/hooks_vbulletin.xml to 0666 (Will not function without this done!)


Enjoy :)

- Zero Tolerance

Whose been busy then :) I'll be giving this a tryout at some point.

Presumably if you upgrade your vB, you need to add all the custom hooks again - does this keep a record of the ones you have added ?

The XML file keeps a record of all custom hooks, like the default vB system does, in the next version it will "fully" support other xml files, as vBulletin built in the ability to have multiple hook xml files, however mine doesn't "fully" work with that and relies on the master one given by vB, so i'll ensure it's running through it's own so upgrades shouldn't effect anything, unless a PHP file is re-uploaded, then a hook would need to be re-done, i'll create a lil system for this which will check all the hook calls are in the files, and if not, add them in.

Once that's done really, no one would need to bug vB anymore for hook locations :)

- Zero Tolerance

Hmm .... not really. If you are using custom hooks you must edit the PHP files, if there are standard hooks you can easily upgrade without having to re-apply file modificatiosn.

This edits them for you, and the repair system i'm including will correct all custom hook installations if you have just upgraded your vB :)

- Zero Tolerance

Hmm, this is like vBHack - a system that automatically alters your PHP files.
Don't like the idea too much ...

how would it know where to add them - line numbers are bound to change.

True, but it's only altering 1 line (for each hook), the only way it could mess up your system was if you inserted a hook onto a line where it should be, like inbetween if() and {, ofcourse you can delete the hook if errors occur (once i get the next release done).

@ Paul - That's upto you to keep things updated, the PHP will change over time, so it would be best to keep the hooks updated and ensure there in a safe place, if there nested inside a lot of code, chances are in the future it would cause problems, but if it's out of the way in a distant area, then the chance is smaller. Unfortunatly there isn't much i can do about this, even if you put in a search term to insert the hook after/below, the PHP again could be changed within the future.

- Zero Tolerance

Here's the main problem: line numbers change.

Then feel free to give me an alternate method that would eradicate that problem and not cause any others - i'm all ears =P

- Zero Tolerance