> <cfoutput>#MyVar#</cfout (improperly closed tag)
> OR
> <cfoutput>#MyVar</cfoutput> (var not enclosed in ##)
Hi
One approach that I've used is... (pretty much covering the same ground
Ewok did!)
<!--- Variables.isDebug is tied to an environment variable which either
shows the errors in 'dev', might in 'test' and never in 'production'
--->
<cfif not variables.isDebug>
<cferror type="request"
template="../_display/_dsp_error_request.htm"
mailto="#variables.errors.toEmailAddress#" />
<cferror type="exception" exception="any"
template="../_display/_dsp_error_any.cfm"
mailto="#variables.errors.toEmailAddress#" />
</cfif>
On the _dsp_error_request.htm you can use limited cferror variables as
this is a _bad_ error
On the _dsp_error_any.cfm you generally have full CFML functionality
available to you (ie email you a message etc)
For further error handling, in _dsp_error_any.cfm you can have a psudo
fusecircuit that uses #error.rootcause.type# to switch and carry out the
require action.
The REQUEST one will def catch the ones you have asked about but you may
be able to catch them via a specific excetption.
Cheers
--
dc
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
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:204466
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=89.70.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
