So what you are now saying is that your method will not work, and you have been lucky to this date to not run into it.
Until we see the code that delivers the PDF, you have to look at what is causing the compile error. It has nothing to do with when one is compiled or not, or what order it is compiled in. ColdFusion will always compile application.cfm/application.cfc and then the template you are trying to run, and onRequestEnd.cfm if you have it. It can't do it any other way, because it has to know what variables might be defined in the application.cfm. The problem that you can't comprehend is that you are wrong. Like I said in another post, I give up trying to help you now. You have been told to look at what is causing the error, the error is the PDF. You have admitted that another PDF will work fine, so what makes your template and this PDF crash with an excpetion, and stop compiling the code? Now I know for a fact that Application.cfc/Application.cfm is the first thing in the chain, it has to be executed before the template you are calling, because if it didn't you can't access those variables that you define in there, now can you? Regards, Andrew Scott http://www.andyscott.id.au/ > -----Original Message----- > From: Claude Schnéegans <[email protected]> [mailto:=?ISO- > 8859-1?Q?Claude_Schn=E9egans <schneegans@interneti=71?= =?ISO-8859- > 1?Q?ue.com=3E?=] > Sent: Thursday, 23 June 2011 11:50 PM > To: cf-talk > Subject: Re: application.cfm > > > >>Now if you are 100% confident that your PDF is being delivered by the > cfcontent tag, then it sounds like you may have come across a bug. > > No, the pdf is not delivered in case of an error, since it is a compile error, no > code is executed. > For years I've been using this trick, and no file even contained any occurrence > of the string "<CF". > Note that any file containing anything except "<CF" will pass through the CF > compiler with no problem. It was the case for years. > > And it is not a bug in CF if this is what you mean, is is just the way it works. > As I said, it could have been > 1. compile application.cfm > 2. execute application.cfm... and eventually abort here. > 3. compile the requested template > 4. execute it > > It is rather > 1. compile application.cfm AND the requested template 2. execute > application.cfm... and eventually abort here. > 4. execute the requested template > > There may be a good reason I don't know to do things in that order, but it is > certaily not pure logic. > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > ~~~~~~~~~~~| > Order the Adobe Coldfusion Anthology now! > http://www.amazon.com/Adobe-Coldfusion- > Anthology/dp/1430272155/?tag=houseoffusion > Archive: http://www.houseoffusion.com/groups/cf- > talk/message.cfm/messageid:345577 > Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm > Unsubscribe: http://www.houseoffusion.com/groups/cf- > talk/unsubscribe.cfm ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:345583 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
