should fail.
It seems like the error could be misleading and being thrown at the CFFF
rather than the CFINCLUDE - try commenting out the CFINCLUDE and see if you
still get the problem.
If you do then you know, at least, that the error message is less than
specific. ;^)
Jim Davis
_____
From: Ken Ferguson [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 19, 2004 10:49 AM
To: CF-Talk
Subject: RE: BlueDragon cfinclude issues
Nope, same result.
Also, <cfoutput>#variables.incfilename#</cfoutput> gives the same value
as <cfoutput>#evaluate(variables.incfilename)#</cfoutput>
The evaluate just got in there as I was playing around with things. It's
not really useful in this code. Remove all the evaluates and you still
get the same thing.
_____
From: Scott Brady [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 19, 2004 9:42 AM
To: CF-Talk
Subject: Re: BlueDragon cfinclude issues
You have this block:
<cfif fileexists(evaluate(variables.incfilename))>
<cfinclude template="#variables.incfilename#">
<cfelse>
...
I think the issue is that you're testing to see if
"Evaluate(variables.incfilename)" exists, but then you're only
including "variables.incfilename". Try <cfinclude
template="#Evaluate(variables.incfilename)#" > Instead.
Or, better yet, find a way to get rid of the evaluate. (I haven't used
BD, but Evaluate is probably slow as it is in Macromedia CF)
Scott
--
-----------------------------------------
Scott Brady
http://www.scottbrady.net/
_____
_____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
