I have to agree with Dark Visor. As a non-experienced coder, I can say this was really hard to understand. I was searching for an explanation of how adding options to a product via the admincp works and there was nothing like that there.
I have to agree with Dark Visor. As a non-experienced coder, I can say this was really hard to understand. I was searching for an explanation of how adding options to a product via the admincp works and there was nothing like that there.
This is because this is an documentation of the API of vBulletin. These types of documents are simply a list of classes, functions and the variables they expose. It is not a programming manual to teach you how to program or expand the system. Rather it is a list of things you can reference in your code. And while it is sparse (i.e. doesn't tell you how all variables are used or what they mean), that can be expanded upon in the future.
It is not meant for people who are not experienced in PHP programming or who are just learning. If you are just learning, I would suggest looking in the Tutorial's forum on this site and the developer documentation in the Online Manual.
This is because this is an documentation of the API of vBulletin. These types of documents are simply a list of classes, functions and the variables they expose. It is not a programming manual to teach you how to program or expand the system. Rather it is a list of things you can reference in your code. And while it is sparse (i.e. doesn't tell you how all variables are used or what they mean), that can be expanded upon in the future.
It is not meant for people who are not experienced in PHP programming or who are just learning. If you are just learning, I would suggest looking in the Tutorial's forum on this site and the developer documentation in the Online Manual.
Adding settings in a product via the vBulletin GUI, is not a programming issue but a vBulletin issue. However it's not explained either in the online documentation nor in the API documentation.
Hopefully as time goes on the documentation can be improved and we can provide a developer's guide or a programming vBulletin guide. However, this isn't the purpose of the API documentation.
I have to give my compliments as well. I'm exactly the kind of coder that craves docs this detailed. I've spent far too much time combing through vB code I don't understand completely.