[How-to] Hooks and Plugins

[calorie]

In hooks_vbulletin.xml you will see things like the following:


Code:
---------------
Code is only visible to licensed users, and only when logged into the forums.
---------------


The hooktype is just a unigue name for the hook tags within. The hook tags refer specifically to PHP code in the vB files.

The PHP code in the vB files looks like the following:


Code:
---------------
Code is only visible to licensed users, and only when logged into the forums.
---------------


Note how global_start is in a hook tag in hooks_vbulletin.xml and also in the vB PHP code.

To make a plugin hooked to global.php, you create an XML file as follows:


Code:
---------------
Code is only visible to licensed users, and only when logged into the forums.
---------------


The place in vB PHP code where your global_start plugin runs is where the following occurs in global.php:


Code:
---------------
Code is only visible to licensed users, and only when logged into the forums.
---------------


Basically, you make plugins via XML and your plugins hook to vB PHP code
via <hookname>hook_name</hookname> from the plugins,
which needs to match the fetch_hook('hook_name') in the vB PHP code,
which needs to match <hook>hook_name</hook> in hooks_vbulletin.xml.

You can even make a plugin that hooks to multiple vB PHP files as follows:


Code:
---------------
Code is only visible to licensed users, and only when logged into the forums.
---------------


This latter example runs the first batch of PHP code where the following occurs in global.php:


Code:
---------------
Code is only visible to licensed users, and only when logged into the forums.
---------------


And runs the second batch of PHP code where the following occurs in index.php:


Code:
---------------
Code is only visible to licensed users, and only when logged into the forums.
---------------


Again, note how <hookname>hook_name</hookname> in the XML plugin
matches fetch_hook('hook_name') in the vB PHP code
matches <hook>hook_name</hook> in hooks_vbulletin.xml.

Further readings...

What is a hook:

- http://www.vbulletin.org/forum/showpost.php?p=665079&postcount=11

How to make a plugin:

- http://www.vbulletin.org/forum/showpost.php?p=664115&postcount=14

How to add a new hook location:

- http://www.vbulletin.org/forum/showpost.php?p=663701&postcount=1

[ojay]

the devkeys in the opening plugin tags mustn't be equal

[calorie]

Okay, thanks, updated.

[Qualia]

calorie, Thank you for explaining that. I had someone tell me what a hook was and I kind of got my brain wrapped around the idea, but you finished off the explaination really well. I'm a visual thinker and the way you explained how this will work was good for me.

[calorie]

Thanks. KirbyDE was helping me to understand, along with the authors of the other posts I listed, so I'm glad that you found it useful, and that I got to "pay it forward." :)

[Christine]

Thanks calorie -- nice job!

[flup]

I still don't understand much about the plugin and hooks... somebody should write a dutch how-to (Floris maybe?)

[Highlander65]

Are there restrictions on what can go inside the


Code:
---------------
Code is only visible to licensed users, and only when logged into the forums.
---------------


For example:

Can we use a simple include or require statement for large code sections or functions?
Do we have length restrictions?
Can we make new SQL queries?
Is there any PHP code that can't be used?
Is there any PHP code that SHOULDN'T be used (different then can't)?



Stuff like that...
Thanks!

[ToraTora!]

I have ran into several roadblocks on this new plugin situation and it is frustrating to say the least.
Entering in SQL queries seem to work, but eval codes for template calls (even by the new standard like error templates) cause errors.

I am pretty sure it is user error on my end, but what would be really nice to see for once is a real life example of a mysql plugin-template exchange within a plugin so we have a general idea of what needs to be done in order to make it work properly.

Ok, starting to get the hang of it. I still prefer the old way of simply creating a include script to handle all of my hacks, but I can also see where the plugin manager will be beneficial for many areas such as a seperate front page with left, middle and right columns similar to the old Nuke class system.

Are there restrictions on what can go inside the


Code:
---------------
Code is only visible to licensed users, and only when logged into the forums.
---------------


For example:

Can we use a simple include or require statement for large code sections or functions?
Do we have length restrictions?
Can we make new SQL queries?
Is there any PHP code that can't be used?
Is there any PHP code that SHOULDN'T be used (different then can't)?



Stuff like that...
Thanks!

Most of the PHP code does work, but forget old functions such as the bbcode_parse or things along that nature.

The SQL queries will work as well, but you have to use the new format which was posted by VBLuke earlier, in which Keir created a document on those new settings.

A example of what I did with just a very elementary and simple condition within a plugin was this:



Code:
---------------
Code is only visible to licensed users, and only when logged into the forums.
---------------



Which worked. As long as I have that basis and get re-familiarized with many of the new variables, things should be pretty well back to normal within the plugin system, rather than creating a include script for my own created hacks.