different settings for that area.
The example already quoted is for an administration area.
I have an application i'm building now where the client has different
divisions of the business and wants different look and feel for each
division. So I'm using the application.cfm in each folder to hold the
look and feel variables for that part of the business. But the
application.cfm at the root level has things like:
DSN name
Webmaster email address
mail server, mail server name and mail server password
time adjustment for Australian time (application.austime used instead of now())
Request.appmapping - the name of the mapping for the production
version of the site
request.approot - the name of the root url for the production version
of the site
etc etc etc
the different application.cfm files have things like:
request.sectionname - the name of this part of the site
request.headercolour
request.footercolour
request.cssfilename
and also cfinclude the upper level application.cfm
Cheers
Mike Kear
Windsor, NSW, Australia
AFP Webworks
http://afpwebworks.com
.com,.net,.org domains from AUD$20/Year
----- Original Message -----
From: Ewok <[EMAIL PROTECTED]>
Date: Fri, 1 Oct 2004 20:23:45 -0400
Subject: RE: cfinclude application.cfm
To: CF-Talk <[EMAIL PROTECTED]>
I think that's what I just said isn't it? Why use one in every directory if
they are just including the one in the root and all end up with the same
settings.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
