Any reference to a CF template in the following fashion:

        <cf_whatever>

will either be referenced as a native command that CF will see and
understand or it will look to the local directory where the calling template
exists, finally if not found there, it will automatically look to the CF
CustomTags directory.  There is actually nothing you need to do that is
special in anyway as long as you have access to this directory, whether it
is localhost only or on a file server.  And it should have nothing to do
with Advanced Security.

I'm sure there must be other issues at play here.  Perhaps it would be
helpful to see your calling syntax?  I'm hoping that the answers that many
of us have been giving have proven helpful in some way....but you may need
to supply more information to better get a handle on what trouble you are
actually encountering.

Mike

-----Original Message-----
From: David Adams [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 16, 2001 4:43 PM
To: Fusebox
Subject: RE: Common Code Mapping


Ok - this isn't really a Fusebox issue anymore.

I found the CustomTags directory under my Cfusion directory.  Now, my
Cfusion directory is on my E: drive (applications partition) and my wwwroot
is on my G: drive (Data).

How do I force CF to look in the CustomTags directory?  Or, how do I create
a new one?  Does this have anything to do with Advanced Security?  Because I
didn't install that when I set up CF on this machine in the first place.
(BTW, is there a way to correct that problem now??  Can it be installed
now?)

Thanks!

Dave
--
Web Applications Developer
Marconi PLC - MSI Division
425-519-2046

Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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

Reply via email to