You can use the CF_Debugger tag that Alan McC and I wrote. It's available at http://bjork.net/taggallery

Otherwise, use Hal's method. Just drop this is at the top of every template: <CFOUTPUT><!-- #GetCurrentTemplatePath()# --> </CFOUTPUT>

That puts an HTML comment in the HTML source, showing the full path of every template that gets called, in order, and in position (relative to the produced HTML).

YOu can use CF-STudio to drop this code into the top of every template in a directory tree, using Extended Replace, with RegExps:

Replace this: (.*)

With this: <CFOUTPUT><!-- #GetCurrentTemplatePath()# --> </CFOUTPUT> \1

Best of luck, Lee Bjork Borkman ps, if you think FuseBox goes through a lot of tags, just try CFObjects ;-)

--------------

>From: "Daniel J O'Keefe" <dan@tripointtek.com>

>With all of the includes as part of the Fusebox methodology, does anyone >know of some type of trace tag to output a list of templates that were >executed, and IN THE ORDER that they were executed? I just spent some time >looking through the gallery but all I found were tags that used the >CGI.PATH_INFO which does not help you with includes. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm

Archives: http://www.mail-archive.com/fusebox@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists