Thanks for the suggestion. This is the way I've been doing it, but it
breaks code portability. I want the root of the application to be known
from where the application.cfm file resides (I can find this out by doing
some recursive CFDIRECTORY trickery), and not be hardcoding in something
like this.
Thanks anyway,
-R
> -----Original Message-----
> From: Chris Evans [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, April 04, 2000 2:05 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Programatically setting search path for custom tags
>
>
> You can't do it using the CF_ notation for custom tags, but you can if you
> use CFMODULE. The name attribute of CFMODULE uses the custom tags
> subdirectory as its root, then uses dot notation to specify
> subdirectories.
>
> For example, I have a custom tag called wrap.cfm stored in the custom tags
> directory (D:\CFUSION\CustomTags). By default, I could call it using
> <CFMODULE NAME="wrap" TEXT="#string#">. Alternatively, I could put a
> subdirectory for rking and yfeng in the custom tag directory -
> D:\CFUSION\CustomTags\rking and D:\CFUSION\CustomTags\yfeng. I could call
> these custom tags using the dot notation : <CFMODULE NAME="rking.wrap"
> TEXT="#string#">.
>
> In the Application.cfm, you could set a variable (CFSET
> CustomTags="rking.")
> to denote the developers subdirectory, can call custom tags like <CFMODULE
> NAME="#CustomTags#wrap" TEXT="#string#">.
>
> There is an interesting article about this in the April edition of CFDJ.
>
> Chris Evans
> [EMAIL PROTECTED]
> http://www.fuseware.com
------------------------------------------------------------------------------
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
