|
Hi Taco,
do it all the time Taco, and much as Robin
described. also do it for the other little matching template onrequestend.cfm :)
- remember to always make a pair.
I only ever have one cfapplication tag and that is
in the root application.cfm
I only add directory (read - sub-bit of
functionality) specific application.cfm when i want to append/prepend to the
application processing logic provided by
application.cfm/onrequestend.cfm.
I prepend when i want the 'mother' application.cfm
to take action based on the input, and append when i just want to add common
processing/variables.
example - a local appliccation.cfm
<cfset request.directorySecure =
true>
<cfinclude
template="../application.cfm"><!---the next one down, which may or may not
be the 'mother'--->
<cfset request.someGlobal =
35> <!--- for this scope (directory) of code--->
...
example - a local onrequestend.cfm
<cfset request.displayDebugging=
true>
<cfinclude
template="../onrequestend.cfm"> etc
Elliot
--- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/ |
- [cfaussie] RE: Include application.cfm Steve Onnis
- [cfaussie] Re: Include application.cfm Brett Payne-Rhodes
- [cfaussie] Re: Include application.cfm Taco Fleur
- [cfaussie] Re: Include application.cfm Robin Hilliard
- [cfaussie] Re: Include application.cfm Elliot Russo
- [cfaussie] Re: Include application.cfm Steve Onnis
- [cfaussie] Re: Include application.cfm Taco Fleur
- [cfaussie] Re: Include application.cfm Peter Tilbrook
- [cfaussie] Re: Include application.cfm Robin Hilliard
- [cfaussie] Re: Include application.cfm Peter Tilbrook
- [cfaussie] Re: Include application.cfm Barry Beattie
- [cfaussie] Re: Include application.cfm Elliot Russo
- [cfaussie] Re: Include application.cfm Taco Fleur
- [cfaussie] Re: Include application.cfm Steve Onnis
- [cfaussie] Re: Include application.cfm Elliot Russo
