This is an alternative for ColdFusion debugging. This answers the old questions of:
What happens when you are not there?
In particular, it assist with tracing activity of all users that are running requests (not just the developer).It will allow unattended capture of debug information to file system as requests are being made. This will allow developers to look at debug information after the fact.
Flag can be set in code to direct some options including if errors are automatically emailed.

It has the same overhead characteristics as leaving Debug on, so it should be used temporarily.

Usage:
To use this, please copy the file to your ColdFusion debug directory normally located here:
[cfroot]\wwwroot\WEB-INF\debug
Then access your ColdFusion Administrator Debug Settings page and select ToFile.cfm from the drop down menu for Debug Output Format.

Debug files will be written to the ColdFusion temp directory normally located here:
[cfroot]\runtime\servers\coldfusion\SERVER-INF\temp\wwwroot-tmp\U00

When error occurs in processing the file name is slightly adjusted with an [_ERR] appendix for easier problem identification.

The following flags can be provided in either variable, form, or url scope to direct the behavior of the debug processing.
A good place for setting these would be in Application.cfc

DebugSilent => if this is defined the final line at the bottom of the output will be supressed

DebugOnlyErrorToFile => only write files when there is an error (even if caught with cftry/cfcatch)

DebugErrorToEmail => attempt to send Error debug output to this email address

DebugUserIDs => if you are using Session.UserIDs a list of IDs for which to capture debug information.

This has been tested with CF 7 and 8.
Please see code comments on how to install and use.

There are no issues for this project.

To enter issues for this (or any other) project, you must be logged in.