Okay, figured it out.
Both cffile and cfinclude will work.
With cffile you need to output the cffile variable, as opposed to
letting cffile display it directly.
With cfinclude the pathing is screwy. I used a bunch of
up-directories (../) to get all the way to the root of the server
drive, and
For CFInclude, you can use mapped paths (in CF Administrator) to clean your
pathing up.
- Original Message -
From: Jamie Jackson [EMAIL PROTECTED]
To: CF-Talk [EMAIL PROTECTED]
Sent: Tuesday, December 04, 2001 11:04 AM
Subject: Re: Limitations in Missing Template Handler Template
(in CF Administrator) to clean
your
pathing up.
- Original Message -
From: Jamie Jackson [EMAIL PROTECTED]
To: CF-Talk [EMAIL PROTECTED]
Sent: Tuesday, December 04, 2001 11:04 AM
Subject: Re: Limitations in Missing Template Handler Template?
Okay, figured it out.
Both cffile and cfinclude
I'm trying to set up a custom 404 template that can (individually)
handle multiple sites' (CF) 404 errors (they are hosted on the same
server).
I'm having trouble with cfincludes and cffiles within the custom
CF 404 template: I can't get them to work.
Are these disabled to prevent endless 404
I've found that HTTP redirects and cflocations function properly,
but they don't quite have the behavior I need within my custom CF 404
page.
So, I'm still wondering about cfincludes within my Missing Template
Handler page.
Possible, or no? Is there anything special I need to do with the
5 matches
Mail list logo
