I figured it out right after I sent my last message.

CF Cache was preventing your app from seeing changes in CF templates.

Now the app starts.

best,  paul

At 02:02 PM 4/9/01 +0000, you wrote:
>Hi Paul,
>
>As app_globals.cfm is in the config directory, your CFMODULE call would be
>expecting the tag to live in that directory too.  If you put it THERE, and
>it still can't find it, I can only guess that it's the filename case (is it
>a UNIX box?).  As I said, my code would be expecting lower-case filenames.
>
>Anyway, I used CFMODULE with the intention of making the code easier to
>install for all those people who can't access the CustomTags directory on
>shared servers.  If it's turning out to be more hassle than help, then just
>change the two CFMODULE calls to CF_ format custom tag calls.  If anyone
>else is having similar problems, let me know, and I'll get rid of the
>CFMODULE calls in the original.
>
>Thanks,
>LBB.
>
>
>
> >From: Paul Smith <[EMAIL PROTECTED]>
> >
> >Well, I've put FormURL2Attributes.cfm everywhere, including in the same
> >directory as your index.cfm, and your app cannot find it.  I even changed
> >app_globals.cfm to:
> ><CFMODULE TEMPLATE="FormURL2Attributes.cfm" display="no"> and that doesn't
> >work.
> >
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at 
http://www.fusionauthority.com/bkinfo.cfm

Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists

Reply via email to