I have done that on many sites and it works quite well. In most
cases you have just one line in the file in web directory a include of the
fusebox app that you need there. Also make sucurity for the app good
because all your fuse file are not accessible to the public. One more
method of securing the non index files with in fusebox.
Daniel D.
-----Original Message-----
From: Ken Beard [mailto:[EMAIL PROTECTED]]
Sent: Saturday, April 14, 2001 6: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
