Very easy...  The easiest thing to do is parse the logs, but that's a pain. 

In cf server, you can set a global error handling template. Here's the code
because it's Friday and I feel like giving back:


YAY!  Free Code!

<link rel="stylesheet" type="text/css" href="/styles/worp.css">

<cfparam name="url.action" default="">


<cfif url.action EQ "sendmail">
        <cfmail server="#application.smtp#"  to="[EMAIL PROTECTED]"
from="[EMAIL PROTECTED]" subject="Cold Fusion Error" type="HTML">
An Error Occurred In Cold Fusion.<br>
<b>User Info:</b><br>
#form.UserInput#<br>
System info:<br>
#form.debuginfo#
        </cfmail>
<cflocation url="joblisting.cfm">
</cfif>




<form name="error" action="error.cfm?action=sendmail" method="post">
        </td>
<td valign="top">
<table>
<tr><td><span style="font-size: 16pt"><b>Oops, an error has
occurred<br>Please provide us info and click SUBMIT.</b></span></td></tr>
<tr><td>
<textarea name="UserInput" rows="6" cols="80" style="font: 8pt MS Sans
Serif"></textarea>
</td></tr>
<tr><td>Debugging Info (Appdev Only):</td></tr>
<tr><td>

<textarea name="debuginfo" rows="6" cols="80" style="font: 8pt MS Sans
Serif; <cfif session.worpadmin NEQ "1">visibility: hidden</cfif>">
<b>Browser:</b><cfoutput>#Error.Browser#</cfoutput><br>
Remote Address: <cfoutput>#Error.RemoteAddress#</cfoutput><br>

<b>Error:</b><cfoutput>#Error.Diagnostics#</cfoutput><br>

<b>Template:</b> <cfoutput>#Error.Template#</cfoutput><br>
<b>Query String:</b> <cfoutput>#Error.QueryString#</cfoutput><br>

<b>Variables:</b><br>
<table border="0">

<cfloop collection="#session#" item="myVar">
        <tr>
        <td>
                <cftry>
                <cfoutput>SESSION.#myVar#</td><td>#evaluate("session." &
"#myvar#")#</cfoutput>
                <cfcatch></cfcatch></cftry>
                </td>
        </tr>
        </cfloop>
        <br>
        <cftry>
        <cfloop collection="#form#" item="myVar2">
                <tr>
                <td>
                        <cfoutput>FORM.#myVar2#</td><td>#evaluate("form." &
"#myvar2#")#</cfoutput></td>
        </cfloop>
        <cfcatch></cfcatch>
</cftry>
</table>
</textarea>


</td></tr>
<tr><td>
        <input type="submit" value=" Submit ">
</td></tr>

</table>
</td>
</table>
</form>

-----Original Message-----
From: James Sleeman [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, February 27, 2002 7:13 PM
To: CF-Talk
Subject: Bug Tracking Systems


Hi all,
        I'm thinking about offering a bug tracking system for our clients
(during 
testing stages of course, I'd never have a bug in a production system :-)) 
for the various jobs they have running with us (i.e we'd have a number of 
projects with each client that they can open bugs with, but each client may 
not see another clients projects or bugs).

Before I invest energy into reinventing the wheel, does anybody know of any 
bug tracking systems written in CF that I might be able to massage to fit 
my needs ?

---
James Sleeman

______________________________________________________________________
Get Your Own Dedicated Windows 2000 Server
  PIII 800 / 256 MB RAM / 40 GB HD / 20 GB MO/XFER
  Instant Activation · $99/Month · Free Setup
  http://www.pennyhost.com/redirect.cfm?adcode=coldfusionb
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists

Reply via email to