Hardcoding paths doesn't necessarily help you when you are moving applications around. It makes some things easier, and some things harder, eg: * If I use hard-coded paths, and I move application X, then I have to change all of X's internal links, as well as links from Y and Z to X. * If I use relative links, and I move application X, then I don't have to change any of X's internal links, although I do have to change all of the links from X to Y and Z.

That's why I use relative links for internal links, and hard-coded for links to other apps. When I move an app, all of my internal links go on working, and I just have to adjust my inter-app links, usually by changing a single variable somewhere in my config.

As for custom tags, I would usually have a set of request-scope variables defining the webroot, the filesystemroot and the application root. My custom tags can use all of these values to build URLs, etc as necessary. I would rarely, if ever, try to refer directly to "index.cfm" from within a custom tag.

Best of luck, LeeBB

>From: "Ben Koshy" <ben@w3media.net> > >Hi Lee, > >I'm using standard Fusebox. Its always bothered me (this question) as I >know when I'm calling these circuits as Custom Tags or with includes I'm >hoping the behavior won't thrown an error or something. Why not use >hardcoded paths? Just in case you want to move the circuit to another >folder? > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 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