Hey Geoff, > My only concerns really are that CFERROR seems an unlikely candidate for > placing in the getDisplay() function. Wouldn't we be better putting > CFERROR in the Application.cfm and CFTHROWing a properly described error > from any relevant method?
I hear ye. > The primary reason for supressing errors in the presentation layer was > for container content gone bad. This could potentially lead to lots of > pages being knocked out from a single piece of corrupted data or > programming. However, error supression appears to have become a default > in other areas where it should not be. > > I'd personally prefer to see all errors thrown with the exception of > containers. And we're trying to work towards that in the next release. Yeah, i guess. I dont use containers at all, so I haven't thought about it. I do like the idea of using error template in the application folder if it's available, regardless of where the CFERROR is. Geoff, have you any changes planned for the way farcry deals with 404s, or would you like me to take a look at this? Any suggestions (from anyone) about how this should work? At the moment we just get the home page, with no error message or http 404. I was thinking of a samilar system to my changes for error capturing whereby if you have a 404 template in your application folder farcry uses this, if not it uses one in the core. Regards 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/
