Developer docs?
 

Hi there,

I need to code a small modification in vbulletin, but I didn´t found any valuable docs that explain how vb works (developer view).

Anyone could tell me where are them? Thanks in advance, Simon.

The PHP Docs for vBulletin are at

http://members.vbulletin.com/api

Also, here is an index of some pretty valuable tutorials/articles:

https://vborg.vbsupport.ru/showthread.php?t=99570

Thanks Danny... but, that´s all the docs about hacking vb? There is only an api and some user tutorials? I expect to see a more structured information about hacking vb...

Well what would you like to know?

Well, a good starting point will be:

• Detailed docs about how vb works from the first request.
• Detailed docs about all the hooks available.
• Detailed vb plugin development guides (why if not made the plugin system?).

All in a structured way.

Suggest them then =]

I agree. I've been learning by reading through the code and trying to figure it out. I think the main point here is that the tutorials were developed by vbulletin customers, not by jelsoft. The sum total of what has been provided by Jelsoft is the API documentation and what is already in the vbulletin manual (in the developers section), which is great, but very limited.

The API documentation seems to have been auto-generated using the comments found within the existing code, and many of the functions themselves have not been documented, meaning that to figure out what they do involves jumping into the code (line numbers don't seem to correspond either) and trying to figure it out.

I think the product and plugin system for vbulletin is a great idea, and makes it really easy for the community to extend the functionality of vbulletin and easily share products and plugins with each other. However, it would be nice if Jelsoft could support this effort a little more by making life a little easier for those who are just starting out. Don't get me wrong, the tutorials are great (and I've written some of them), but I just feel like these tutorials have come as the result of a lot of head scratching and reverse engineering (at least that's how it was in my case).