Hi Gavin,
I've already added this to the core in the p230 branch during the
project I helped Jeff Coughlin with.
If you add the following to your _serverSpecificVars.cfm you should
find that errors are rethrown.
application.bSuppressDisplayErrors = false;
The default behaviour is as before.
The approach I used was to add the following to any cfcatch blocks
that needed it:
<cfparam name="application.bSuppressDisplayErrors" default="true">
<cfif NOT application.bSuppressDisplayErrors>
<cfrethrow>
</cfif>
Spike
On Thu, 10 Mar 2005 13:29:33 +1100, Gavin Cooney <[EMAIL PROTECTED]> wrote:
> Hi Farcryers,
>
> I've never liked the way that farcry hides errors from the user,
> unless they have debug=1 on the url. So, I reckon it's time i did
> something about it!
>
> I know there are <CFCATCH>s all over the core, in the admin etc, but
> i'm only really worried about errors in public facing pages going
> unnoticed and unlogged.
>
> I've looked at the problem, I'm thinking, I just need to change the
> cftry/cfcatch in types.cfc
> where it includes the display method.
>
> Then call a error processing custom tag in the core.
>
> The custom tag looks for a error template in
> /farcry/{projectname}/error_handlers/
> and if so calls that using cfmodule. If no custom page exists, it just
> shows a standard error page. And of course then we can have different
> error templates for different sites... emailing details to developers
> etc etc.
>
> Any further suggestions on how this should work?
>
> Cheers
>
> Gav
>
> ---
> You are currently subscribed to farcry-dev as: [EMAIL PROTECTED]
> To unsubscribe send a blank email to [EMAIL PROTECTED]
> Aussie Macromedia Developers: http://lists.daemon.com.au/
>
--
--------------------------------------------
Stephen Milligan
Code poet for hire
http://www.spike.org.uk
Do you cfeclipse? http://cfeclipse.tigris.org
---
You are currently subscribed to farcry-dev as: [email protected]
To unsubscribe send a blank email to [EMAIL PROTECTED]
Aussie Macromedia Developers: http://lists.daemon.com.au/