Bruce McKenzie wrote: > I was inadvertently upgraded (by hosting service) from v 1.4 to v 2.03 > which is evidently not backward compatible.
I did try to make it as backwards compatible as I could, but that wasn't the primary goal with the new version. > However, I've also found that I can't produce an error page from > CGI::Carp -- if there's an error in a template or module, the only > message I get is the unhelpful "Internal server error". You might look at using the error_mode built into C::A to handle errors. There's some talk here on the list of yet to improve this, and I think Mike Freidman is working on a plugin to make it better. Also, what's wrong with looking at the server's error logs? I almost never want to sent the real error to the screen since it could be shown to users who would either be very confused, or given more information than they should. Even in development I use the error log since it means I don't have to change anything before pushing code out. > Anyone know how to change this behavior? Dispatch tries to be smart about the way it handles errors. To do this it wraps the application's run() method in an eval and examines any execptions thrown to see if they should be converted to NOT_FOUND or SERVER_ERROR message (under mod_perl). I haven't tested it, but maybe you could add CGI::Carp to your Dispatch class. -- Michael Peters Developer Plus Three, LP --------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/[email protected]/ http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
