That is true. Unless an Application.cfm file is found CF will not look for a OnRequestEnd.cfm template. So I guess these two templates are mutual and only work together.
OnRequestEnd.cfm is handy for things like copyright messages at the bottom of you templates. The only way to prevent an OnRequestEnd.cfm template from executing is with a CFABORT tag. You cannot prevent a Application.cfm tag from being executed however. Peter Tilbrook Manager, ACT and Region ColdFusion Users Group - http://www.actcfug.com 4/73 Tharwa Road Queanbeyan, NSW, 2620 AUSTRALIA Telephone: +61-2-6284-2727 Mobile: +61-0439-401-823 E-mail: [EMAIL PROTECTED] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kay Smoljak Sent: Wednesday, 22 September 2004 12:38 PM To: CFAussie Mailing List Subject: [cfaussie] Re: OnRequestEnd.cfm (was Re: Include application.cfm) I've heard people recommend putting an empty Application.cfm file in a directory to prevent CF wasting time wandering up the tree looking for one, but as I understand it an OnRequestEnd template only gets executed when found in the same directory as an Application.cfm template, so there'd be no reason to have blank ones. Maybe the previous developer either misunderstood that, or prehaps had code in there at one point which was subsequently removed. K. --- 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/
