or <cfmodule name="#someplace#my_tag">
Where #somepath# is a path to the tag, same as the template attribute in a cfinclude.
If you use the "name" attribute then #someplace# is a dot delimited location relative to the custom tags directory.
IMO, using cfmodule is far preferable to <cf_...> since it gives full control over which version of a particular tag you're running. Aside from having to change all your <cf_...> tags (Studio regex search and replace...) the only thing you'll need to watch is if any of your custom tags already use "name" or "template" as attributes. Oh, and if you nest tags in a single template then you'll have to ensure your end tags are correct, which may require a bit of tweaking....
If you really want to change the actual Custom tags path then you can do it using cfregistry (for CF5 or earlier - not sure about cfmx), but you probably don't want to go writing and refreshing the registry with every request...
HTH
Bert
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
