oh you poor thing...programming AND having to type...what a tragedy. Ok
that was sarcastic and I don't mean to be cruel but this excuse for not
doing things the right way is really annoying to me as I have heard it many
times before, like let's use the variable name "a" when it stands for
"employeeid".
Personal issues aside (I am seeing a doctor for this problem), you should
not only create only one developer mapping for the root of your site as
#request.cfroot# AND a request variable to store the root for NON <cf> tags
(like <IMG> for example (called request.webroot by the way) but I have found
in several of my implementations, expecially the larger ones, that if I put
the following code:
urlstring = cgi.path_info;
urlstring = reverse(urlstring);
urlstring = mid(urlstring, find("/", urlstring, 1), len(urlstring));
urlstring = reverse(urlstring);
request.pathinfo = urlstring;
in my app_server or app_globals, which will be included in EVERY page
rendered, that I now have a generic variable that will ALWAYS point to where
my current circuit is. This has proven to be incredible helpful when
circuits have to move around or even just components of circuits. If
everything uses those three variables for directory pointers, you will never
have to worry about something not working just because you moved it.
Hope that offers a little insight.
Mike
-----Original Message-----
From: Douglas Brown [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 05, 2001 10:52 PM
To: Fusebox
Subject: structure question
I am creating a fusebox app with about 500 tables and about 20 different
folders, inside each sub-folder I have three other folders called (qry, dsp,
act) and my question is should I create a development mapping to all folders
that will hold templates or should I create a single mapping and use
#request.cfroot# in the index.cfm of each primary folder? I hate typing out
these long lines for the path to the folders using #request.cfroot# but if I
should do it, I will.
Thanks
Doug
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
