"Dan Haley, you fail to grasp Ti Kwan Leep. Approach me that you might see."
There's a very simple solution here...
"Observe closely, class. Boot to the Head! (SH-ZOOMP!)"
<cfinclude template="../Application.cfm">
It's always handy to have an Application.cfm for each directory. ;)
-----Original Message-----
From: Dan Haley [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 22, 2000 11:07 AM
To: '[EMAIL PROTECTED]'
Subject: RE: OnRequestEnd.cfm
Ahh, but there is a flaw in your explanation, grasshopper. It will recurse
the directory tree for application.cfm, and use the onrequestend.cfm from
that directory. So, if you have an onrequestend.cfm in the calling
template's directory, but no application.cfm, it will not use it.
Onrequestend.cfm, if in the same directory as application.cfm, will be used
when that application.cfm is used, otherwise it will be ignored.
Dan
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
