Another consequence of emailing errors, if you are sending diagnostic info with the error (and you should be), you could be emailing passwords, credit card numbers etc. etc. that are passed in the form scope. Consider that when developing your error handling. I like to store them in a db, with a fallback to a write to disk. I only email myself a 'you've got errors' email, if I send the email at all as opposed to checking the log (I use a server monitor to find things like dead db's killing the site). Hand in hand with that is a cfscheduled task that deletes all errors older than X days.
Also, consider using a site wide error handler AND a cferror tag AND, on a granular level, cftry/cfcatch. Use cftry/cfcatch to protect individual blocks of code where you want a specific error handled a specific way (like a mime type failure on an upload). Use cferror as your application's general error handler and use a sitewide handler to bat cleanup in case something goes wrong with Plans A and B. -- --mattRobertson-- Janitor, MSB Web Systems mysecretbase.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:221503 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
