One thing I've done at times is if you've got a directory, you set the
default document to be "index.htm" or whatever, and make that index.htm page
do a redirect, with the appropriate fuseaction appended to the url. This
way, folks who want to go to "foo.com/sales" can do so, without knowing it
really is
"foo.com/sales/index.cfm?fuseaction=mainpage&username=anonymous"...
Even if you have a totally gnarly subdirectory structure, you could create
user-friendly virtual directories (I'm thinking IIS on NT here, I'm sure
there is a .nix equivlant) such as "sales", "info", or whatever, and to the
abovementioned trick to redirect the person to the real stuff.
Of course, you can do the same thing by making a default fuseaction for
every subdirectory, and make that fuseaction load the home page for that
subdir.
> -----Original Message-----
> From: Ken Beard [SMTP:[EMAIL PROTECTED]]
> Sent: Saturday, April 14, 2001 2:03 PM
> To: Fusebox
> Subject: Re: Survey on directory structure usage
>
> I have definitely had feedback from clients and such
> non-coding types that they would prefer to have
> www.website.com/products/index.cfm?fuseaction=list
> to www.website.com/index.cfm?fuseaction=products.list
> and that they would ultimately prefer to see
> www.website.com/products/list.cfm?yadda or even
> .....products/list.cfm with no ?yadda. Why is this?
> two reasons..
>
> 1. to a non-programmer, everything after the ? is
> affectionately known as "gobbledygook" and hence is
> ignored because it has no meaning.
>
> 2. from our client's perspective it is more
> conventient to tell a customer or client check out the
> investor information on our website at
> www.oursite.com/investors than to tell them to go to
> www.oursite.com and click on investors on the menu at
> the top of the page (which they will need help
> finding).
>
> I prefer to route all page calls through a central
> index.. but the customers want multiple directories.
> I have not tried this yet, but what if we structure
> our site like
> /fbsite/ - put the whole fusebox site here, out of the
> webroot.
> /website/ - put a bunch of mostly blank files here
>
> and then maybe even have the fuseminder script or
> something similar that works off an already-written
> set of index.cfm files create a bunch of
> sub-directories and (all but) blank cfm files off the
> /website/ directory, which is where the domain would
> be mapped to.
> Then have an application.cfm file in the /website/
> directory that uses the extra directories and filename
> as the fuseaction, with something like the following:
>
> <cfscript>
> url_website="www.StanCoxRocks.com";
> cfPathToFBSite="/fbsite/";
>
> extradir=right(cgi.path_info,len(cgi.path_info)-len(url_webapproot));
>
> if(len(extradir)){
> fa=replace(extradir,".cfm","");
> fa=replace(fa,"/",".","all");
> if(right(fa,1) is "."){
> fa=left(fa,len(fa)-1);
> }
> attributes.fuseaction=fa;
> }
> </cfscript>
>
> <!--- call the fusebox site --->
> <cfinclude template="#cfPathToFBSite#index.cfm">
> <cfabort>
>
> We would have to do something similar for links and
> cflocations to keep this formatting throughout a
> client's visit to the site. When 5.0 arrives we could
> make a udf.
>
> =====
> Ken Beard
> cfug manager
> Tampa, FL
> [EMAIL PROTECTED]
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
