Lord, some good suggestions came out of this question, but they sure seem
complex. The answer is simple to understand but difficult to explain.
These answers are just as correct but perhaps a bit more advanced than what
you might need...or at least a little harder to explain if you have not seen
this technique before.
If you have a CF mapping to the "root" of your site (let's say its
/mysiteroot), then you can simply reference bodycontent.cfm as you would any
other module call in whatever directory you see fit:
<cfmodule template="/mysiteroot/customtags/bodycontent.cfm">
</cfmodule>
Or, as one comment to this question pointed out, create a common request
level variable in your fusebox'd site that points to that directory for your
<cfmodule template="#request.customtags#/bodycontent.cfm">
</cfmodule>
The important thing to remember is that if you cannot use the CustomTags
directory that you must use either the root mapping (usually "/" which
points to inetpub/wwwroot or a custom mapping which points to some other
place, into which you then create a home for your custom and common
templates.
Mike
-----Original Message-----
From: David Adams [mailto:[EMAIL PROTECTED]]
Sent: Thursday, March 15, 2001 7:57 PM
To: Fusebox
Subject: Common Code Mapping
Help! I can't find the answer anywhere (and I've looked! Just not in the
right places!).
I want to put bodycontent.cfm in a common place and not have a copy of it in
every application directory.
How do I make this happen?
Thanks!
Dave
--
Web Applications Developer
Marconi PLC - MSI Division
425-519-2046
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
