Jared Rypka-Hauer - CMG, LLC wrote:
Nando,
WIthout the CFINCLUDE being executed (which it's not because of pre-compiled code) you're not getting a missing include error.
Because your include is effectively missing and your include path was invalid for the deployment platform, your UDF really IS missing because that include file never really got included.
You might try changing your include like this:
<cfset includepath = "/udf/url.cfm"> <cfinclude template="#includepath#">
Change the path, compile for production, deploy, and then change back to dev. Or compile against a separate set of files.
Either way, your UDF is missing and undefined because your paths are wrong, but you're not seeing the normal errors because you've skipped the runtime compile process that returns certain types of errors in CF.
On a side note, I usually like to pass in my UDF.cfc alread instantiate with my init() arguments for each cfc. Since objects are always passed by reference, I don't see a problem with it.
-- Peter J. Farrell :: Maestro Publishing
blog :: http://blog.maestropublishing.com email :: [EMAIL PROTECTED]
Create boilerplate beans! Check out the Mach-II Bean Creator - free download. http://blog.maestropublishing.com/mach-ii_beaner.htm
---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com).
CFCDev is supported by New Atlanta, makers of BlueDragon http://www.newatlanta.com/products/bluedragon/index.cfm
An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
