PDA

View Full Version : Good programming reference guide for vBulletin 3.8


rEd86
05-15-2009, 05:54 PM
Greetings.

I recently purchased vBulletin and I want to write some plugins/products. There are dozens of great plugins that I have downloaded and reviewed the source to get an idea of what's involved. I have read through the vBulletin API (http://members.vbulletin.com/api/) (what little there is) as well as the vBulletin 3.8 Manual (http://www.vbulletin.com/docs/html) but I am looking for more.

Is there a good reference guide/article you would recommend to help with some of the more advanced concepts? I want to understand what hooks are exposed and what I might be able to extend. I've learned a lot through reading through other people's code but I want a complete list of hooks so I can determine the best approach for some of the things I want to do. (extending the UserCP, etc)

Thanks for your help.

--Ed

troybtj
05-15-2009, 11:06 PM
I, too, am looking for such a reference. I've made a large number of modifications, and would like to package one or two into actual products here. I'd prefer they were fully compliant before doing so, however. :)

rEd86
05-16-2009, 12:22 AM
I do see the "Hook Locations" list in the "Adding or Editing a Plugin" section in the AdminCP and while the names make some sense, having a more detailed description and discussion about what order they get fired off during various tasks would be helpful.

Also, some best practices on modifying UI would be useful. I really like how vBulletin has separated the plugins from the core code. It looks like it's going to be a LOT easier to manage/maintain than phpBB.

--Ed

Lynne
05-16-2009, 02:28 AM
Turn on debug mode and you get a list of all the plugins called on that page at the bottom of the page. I think they are in order or when they first get called.

You might want to look through the Articles forums and see if there is something helpful there.

Dismounted
05-16-2009, 05:21 AM
A good tool to have is a mass search tool, in which you can quickly find where hooks are physically located inside a file.