Hi Toad,
It looks like you have the previous version. If you get the latest from
Bjork.net, it should be fine.
Basically, there is some code in there to try and discover your web
document-root. The old version didn't do a very good job, because it relied
on your CF tree being under /cfdocs. That's not true for your set-up.
Anyway, the new version uses better means to find it out. It should work
fine OR...
....you can just tell it that request.document="D:\INETPUB\WWWROOT". You can
do this is in your FuseBox, or in xfb.cfm, or in your top myGlobals.cfm, but
I think the new version will work fine.
Please let me know how it goes,
thanks for the interest,
Lee.
-----Original Message-----
From: ibtoad
To: Fusebox
Sent: 4/1/01 1:49 PM
Subject: RE: CF_XFB tag - now hiding more unpleasantness...
How do I set up your zip for testing? I keep getting this error:
Error Diagnostic Information
Physical paths are not allowed in CFINCLUDE and CFMODULE
The path you have specified 'D:\INETPUB\WWWROOT\CF_XFB\Circuits.cfm' is
a
physical path that points to a specific drive on your system. Only
logical
paths are allowed in this context. They can be relative (calculated from
the
current directory of the base template) or absolute (calculated using
the
ColdFusion mappings).
The error occurred while processing an element with a general identifier
of
(CFINCLUDE), occupying document position (32:4) to (32:69).
Date/Time: 03/31/01 22:49:32
Browser: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)
Remote Address: 127.0.0.1
Rich
-----Original Message-----
From: BORKMAN Lee [mailto:[EMAIL PROTECTED]]
Sent: Saturday, March 31, 2001 5:58 PM
To: Fusebox
Subject: CF_XFB tag - now hiding more unpleasantness...
Hi all,
The CF_XFB tag now hides all mention of request.circuits, etc.
A top-level index.cfm now looks like this:
<CFINCLUDE template="myGlobals.cfm">
<CF_XFB LOCATION="#getcurrenttemplatepath()#">
<cfif NOT XFB.myaction>
<cfinclude template="#XFB.nextcircuit#">
<cfelse>
<cfswitch expression = "#attributes.fuseaction#">
<cfdefaultcase>
<CF_UnknownFuseAction>
</cfdefaultcase>
</cfswitch>
</cfif>
And a circuits.cfm like so:
<CF_AddCircuits
MyName="scm"
Children="Contacts,UserManager"
LOCATION="#GetCurrentTemplatePath()#">
That's about all there is.
Now available for download at http://Bjork.net/taggallery/index.htm
Let me know what y'all think,
Thanks,
Bjork.
IMPORTANT NOTICE:
This e-mail and any attachment to it is intended only to be read or used
by
the named addressee. It is confidential and may contain legally
privileged
information. No confidentiality or privilege is waived or lost by any
mistaken transmission to you. If you receive this e-mail in error,
please
immediately delete it from your system and notify the sender. You must
not
disclose, copy or use any part of this e-mail if you are not the
intended
recipient. The RTA is not responsible for any unauthorised alterations
to
this e-mail or attachment to it.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
