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

[eXtremeTim]

I can honestly say that what me and zt have been talking about sounds amazing. I know all my hacks will use this system to avoid file edits.

[Dream]

this is creepy, but ill test it out, running a test forum anyway

[eXtremeTim]

wait till you see the next version.

[Zero Tolerance]

v2 released, this is what eXtremeTim gave me the idea about and was excited about

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!.

Enjoy

- Zero Tolerance

[eXtremeTim]

I can tell you this so far this hack looks great.

[Frenck]

The button 'Show File Contents' seems not to work in firefox.


A second one.... I want to add a hook in includes/class_bbcode.php

PHP Code:

        function handle_bbcode_code($code)
        {

                //  THIS IS THE PLACE WHERE I WANT A HOOK....


                global $vbulletin, $vbphrase, $stylevar, $show;

                // remove unnecessary line breaks and escaped quotes
                $code = str_replace(array('<br>', '<br />', '\\"'), array('', '', '"'), $code);

                $code = $this->strip_front_back_whitespace($code, 1);

                // fetch height of block element
                $blockheight = $this->fetch_block_height($code);

                $template = $this->printthread ? 'bbcode_code_printthread' : 'bbcode_code';
                eval('$html = "' . fetch_template($template) . '";');
                return $html;
        } 


How to create one with your plugin? I can't specify only '{' as the line to add the hook below, how to do this nicely?

May you have to expand your option to put a hook not online above or below a specified php line, but maybe also 2, 3, 4, 5 lines above or below...

[FASherman]

After some long thought on this, I'd like to make a proposal to all the entire vb.com community to make allour lives easier.

1. Only hacks that require changes to sql queries should be hacks.

2. Take THIS hack and place it in a seperate forum calls "Add-on Hooks". When a someone codes a hack that can't use a standard hook, they add an add-on hook into this forum. Then they can release their hack as a plug-in. One the add-on hook is released, it can be used by anyone. It becomes an unoffical extension of VB.

3. In the description for plugins, add an additional 2 fields:
Requires add-on hook (y/n)
ThreadID of Add-on Hook.

4. The folsk at VB.Com now have a way to see how many plugins use these add-on hooks. If we have an add-on hook that is used by 20 or more hacks, they know that it should be incorporated into the next release. As they do so, then that add-on hook can be removed from the forum and the hacks updated as full-plugin without add-on hooks.

5. For those of us with hacked boards, all it means is that we have to reinstall our hooks, not the entire hack.

Comments/questions/concerns?

[Ron1n]

i am in love - this hack is great

[macooper]

Hi,
I'm not sure how well this would work, but when patching the linux kernel, they use something called context diffs. Could this be adapted for this mod ?

The idea is that when you add a new hook, your system would take say 10 lines of code before and 10 lines after the hook location. When an upgrade is performed, any hooks in code that has not changed would be easily detected. However, if the 10 lines above / below the code have changed, then you would know that the hook needed redoing manually.

On applying the hooks to an upgraded board, you could then generate a list of failed patches that would need to be added manually. Not perfect, I know, but it would pick up the majority of failed hooks.

Martin

[thermz]

Wow, exceeded yourself again.