> Suggestion... create a standard library of CF files off the
> site root and call it something like "shared". Then put your
> custom tags in that directory. If that doesn't fix your issue
> you could use CFModule... but that should work on any sites.
> I create a set of tags for my apps in /share/sos and then map
> them with CFImport from all my apps to "sos" and call the
> apps like this...
>
> <sos:skin ...>
>
> </sos:skin>
>
> Or public tags in /share/public
>
> <public:myTag>
>
> And that should solve your issues. It's not exactly "how you
> want to do it"... but it sure works.
>
> John Farrar
I have some files like this:
<cfimport prefix="lh" taglib="../extensions/customtags">
<lh:nav>
<h1>Hello</h1>
<cfinclude template="blah.cfm">
</lh:nav>
In this case, if blah.cfm needs to call a custom tag, it needs its own
cfimport line...
So, why can't a cfincluded file inherit a taglib from its 'parent'?
My guess is if blah.cfm was a CFC, having its functionality or resources
being dependent on a library only made available by the invoking file would
be bad...
i.e. blah.cfm wouldn't be a nice self-contained module
Geoff
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to
[email protected] with the words 'unsubscribe cfcdev' as the subject of the
email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting
(www.cfxhosting.com).
An archive of the CFCDev list is available at
www.mail-archive.com/[email protected]
