I have used CFMODULE instead of CF_ form to call the cutom tags. This is done so that poor sould like me who are hosted on shared servers aren't left out. Unfortunately, it it turning out to be quite a problem for many installations.

The supplied file points CTDir to /CustomTags. Now on most CF installations, "/CustomTags" is already mapped to "C:\cfusion\customtags\" (mpte the trailing slash), or wherever the central customTags directory lives. But apparently this mapping is not automaticallay set-up on ALL servers. So you may need to add that mapping on your server.

If you don't want to use, or can't use, the central customTags directory, eg if you are on a shared server, you can make your own, under your own tree. To do this you have to figure out the CF-mapped location of your particular web-root. For example, on Bjork.net, my top-level web directory has a physical location of something bizarre, like d:\etc\webserver\root\users\bjork\www. But the CF-server has "/" mapped to "d:\etc\webserver\root\". So I put a CustomTags directory at the top of MY tree. I therefore set CTDir = "/bjork/www/customtags/".

I know this is all tacky, but I haven't seen a better way around it.

If you are still having problems, and you have access to central CustomTags, just change the 2 CFMODULE calls and their closing tags to normal CF_ format.

Does anyone have any ideas of how best to cope with this problem? I am still looking for a god, free Windows Installer program that will prompt everyone through the installtion process and fill in the appropriate settings. ??

Thanks very much for all or your patiences ;-)

Lee.

>From: "Mike Collins" <mike@w3z.com> > >McCollough, Alan, 19 Apr 2001, at 8:59 sent this: > > > WHat I did was I changed the call to formurl2attributes to a straight > > <cf_formurl2attributes>. > >No go. > > > After that, I get a fight with the cfbodycontent call, which I changed >to > > <cfmodule name="bodycontent"> > > > > <!--- > > > Define the location of the CustomTags directory > > > The location should be an absolute CF-mapped location. > >I think the key will be in figuring out what is meant by an >absolute CF-mapped location. Should I create a mapping in >Studio or specify the full path when setting request.CDDir >below? > >Still scratching my head. I've tried adding a full path, >i.e. c:/cfusion/customtags but it didn't work. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm

Archives: http://www.mail-archive.com/fusebox@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists