Joe Velez began developing for the web in 1998. He is an avid vBulletin user and volunteers his services as a vbulletin.org administrator. He currently spends his time maintaining and developing allnurses.com.
When we first purchase vBulletin, we are approached with the question of where to install vBulletin.
Should we install files in root folder or install vBulletin onto it's own folder--such as "forums"? What is the better option? To me, there is no "better option" but, I will try to lead you into the direction that I believe is the "best option". Hopefully, it will help you in determing where to upload your vBulletin files.
If you prefer option 1; I suggest you install vbulletin in root.
MY OPINION AND TIPS TO YOU:
Install in root
Learn everything about vBulletin...
even if you are not a programmer learn everything about vBulletin's functions and features; read all available vBulletin articles; learn who the key vBulletin coders and designer are, etc
Do not install 3rd party applications that are it's own entity*. eg. PhotoPost, Drupal ...
WORK IS TIME; AND, TIME IS MONEY. 3RD-PARTY APPLICATIONS* INCREASES WORKLOAD
I say this with experience. It may not seem that it adds to your workload at first; but, over time your workload will increase.
Here's something to think about:
Installation and Updates are required on all applications
Learning interface application is required to run application optimally.
You may have to hire more than one coder to help you out on numerous request - therefore, increasing your risk
To run the applications optimally, it is best to read latest news/threads and/or visit site regarding application at least on a bi-monthly basis -- if you have a few apps installed this can be time-consuming.
In some cases, complete integration is not available and application must be hacked. Which in turn -- requires more time since you have to "track all your hacks".
* applications that have their own interface; and, different style of coding --not similar to vBulletin
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
decrease workload
increase revenue (done by decreasing workload)
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 don?t see how creating additional folders for navigation, hierarchical and structural purposes can at all conflict with the websites usability. Rather it would do the complete opposite; by logically organizing your website into subject areas you are ensuring that your users are ascertaining a better understanding of the websites layout.
Although I agree that for instance a good example of integration is Wordpress with vBulletin, Wordpress only requires a singular ./index.php page inside the forum root whilst the remaining configuration files can serve elsewhere in a ./blog/ folder for example. But unfortunately not all products are so forthcoming with their integration.
It makes much more sense for a website to be organised as so; (BTW i am not very good with these virtual diagrams!)
Quote:
/ (homepage root)
!
!
/forums/ -- /blog/ -- /gallery/ -- /directory/ (including appropriate configuration files within each directory)
Rather than the following;
Quote:
/ (homepage root) - forum files -- gallery user files -- blog user files -- directory user files
!
!
/gallery configuration files/ -- /blog configuration files/ -- /directory configuration files/
1)__ What I mean by "usable" is that the URL is shorter ... therefore, easier to remember.
2)__ You are assuming that everyone wants a "blog", "gallery", and/or "portal".
3)__ All 3rd-party applications that you mentioned can work while vBulletin is in root.
Quote:
Although I agree that for instance a good example of integration is Wordpress with vBulletin, Wordpress only requires a singular ./index.php page inside the forum root whilst the remaining configuration files can serve elsewhere in a ./blog/ folder for example. But unfortunately not all products are so forthcoming with their integration.
thank you .. I didn't know that about WordPress
However, you just made my point -- if an application is well thought out you should never ever have to choose between "root" or "folder". The bad thing about WordPress is that it will take you time to learn, install, update, etc, etc. To me, all of this is "time" .. and time is money.
4)__ Like I said on my first post
Quote:
To me, there is no "better option" but, I will try to lead you into the direction that I believe is the "best option". Hopefully, it will help you in determing where to upload your vBulletin files.
02-23-2006, 10:00 PM
02-26-2006, 06:41 PM
