Thanks Adam. I have seen reference to that utility a million times, but in the 
heat of the battle today it just wasn't clicking.

________________________________

From: [EMAIL PROTECTED] on behalf of Adam Churvis
Sent: Wed 6/8/2005 4:41 PM
To: [email protected]
Subject: Re: [plum] Custom Tags



Unfortunately, ColdFusion has no concept of binding a custom tag path to an
application, so all applications share all custom tag paths defined in
ColdFusion Administrator.  ColdFusion will cache the path of the first
custom tag it finds with a specific name, then make all further calls to
that same custom tag.

That's what CF_2CFMODULE is for (see our home page).  We're currently
working on the new Plum Service that handles all this on-the-fly for you as
you work, but until it's released you'll need to use the CF_2CFMODULE
utility.

Respectfully,

Adam Phillip Churvis
Member of Team Macromedia
http://www.ProductivityEnhancement.com

Download Plum and other cool development tools,
and get advanced intensive Master-level training:

* C# & ASP.NET for ColdFusion Developers
* ColdFusion MX Master Class
* Advanced Development with CFMX and SQL Server 2000

----- Original Message -----
From: "Adams, Scott [DOC]" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Wednesday, June 08, 2005 5:10 PM
Subject: [plum] Custom Tags


This may be an old question, but has anyone else had a problem with
Coldfusion using custom tag paths to a old project. I have had this happen
many times on my development server where I have custom tags that share the
same name in two different folders and I cannot get CF to stop using the
custom tags from the old location. I hope this is clear.

Thanks in advance,

scott



**********************************************************************
You can subscribe to and unsubscribe from lists, and you can change
your subscriptions between normal and digest modes here:

http://www.productivityenhancement.com/support/DiscussionListsForm.cfm
**********************************************************************


<<winmail.dat>>

Reply via email to