The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#1
|
|||
|
|||
What is the best folder structure to use for mods?
What is the best folder structure to use for mods?
I like to be able to delete files from mods easily, but there are some trade offs that lead me to place them in the standard folders. If I do that I guess I could name the individual files uniquely so as to make them easy to find. Here's the structure I presently use: /admincp/[mod name].php /packages/[mod name]/[css].css /packages/[mod name]/[javascript].js /packages/[mod name]/hooks/[hooks].php /packages/[mod name]/includes/xml/[xml].xml /images/[mod name]/buttons/[images].jpg Or should it be something like: /admincp/[mod name].php /clientscript/[css].css /clientscript/[javascript].js [mod name hook1].php [mod name hook2].php /includes/xml/[mod xml].xml /images/buttons/[mod images].jpg Or something else? |
#2
|
||||
|
||||
Well if this is mods you are creating yourself, I use something similar to the first way.
Now if this is mods that are already coded, you will just have to load them however the developer has told you to load them. By changing the file structure, you would have to go through every file for each mod, and re write any references to file locations, it would be a PITA. |
Благодарность от: | ||
zylstra |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|