[Razz]

Originally Posted by princeton

if the PRODUCT is well integrated with vbulletin they will have their own "folder" while having vbulletin in root

optimally, an end-user should NOT be directed to a "folder" (eg. /gallery/index.php); this should be done as a last resort

here's an example of how a gallery application should be set up:
gallery.php (root)
depends on gallery setup but you can also have..
newgalleryreply.php (root)
newgallery.php (root)

all related functions and config files should be in GALLERY folder

I don't know about you but my goal as a site administrator is to

1. decrease workload
2. increase revenue (done by decreasing workload)
3. make site usable (Usability) - a good start would be to create short urls whenever possbile

Please understand that I'm not saying that it is wrong to create "folders" for each application. What I'm saying is that ultimately it will cost you more money if you do (time is money).

I disagree, if you think that vB addons such as a gallery shouldn't have their own folder then they also shouldn't have a folder for their functions and configs, these should also be in the relevant vB default folders.

The advantage to having the entire gallery in its own folder and vB in a non root folder is that the urls are better and you can also point subdomains directly to them. e.g forum.domain.com / gallery.domain.com

Each to his own really, both methods have their advantages and disadvantages.