-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
><cfset request.cfroot = "/myapp">
> > <cfset request.webroot = "/">
> <cfset request.imgroot = "/images/">
>
> or whatever you need them to be.
>
> <cfinclude
> template="#request.cfroot#/actions/act_MySuperDuperStudlyActionFile.
> cfm">
I do something similar to this for other operations (img
src=#application.imgdir#/foo.gif), that way I just have a different
set of definitions for these on the production box and can move
around with ease. I can still use absolute references like this for
the cfincludes, right? Presumably if there are no development
mappings, includes just use the normal web server file structure?
c
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8 for message encryption and authentication: USE PGP!
Comment: PGP KeyID: 0x51046CFD
iQA/AwUBOcLyE9aLYehRBGz9EQIAhgCg8KeKPMhzO1DyQ8JH9c4yerMA0E8An2G3
Qhr8meWDsmrvRFGpsPrGU+Fe
=s76n
-----END PGP SIGNATURE-----
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
