https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24574
--- Comment #9 from David Cook <dc...@prosentient.com.au> ---
(In reply to David Cook from comment #8)
> So I think we should require error-handling everywhere. As Jonathan noted,
> it is painful (in our current architecture), but I don't think that's a
> reason not to do it.
If we used more of a MVC model, it would be easier to do high-level
error-handling, as we could just add a general try/catch in the controllers,
and throw a 500 error or something instead with a message like "Sorry, we had
trouble loading this page. Please do X, Y, Z." But... I don't see us
re-architecting any time soon.
Trying to wrap all existing CGI scripts in a try/catch like that would be a
nightmare too though, since there are so many CGI scripts.
I suppose one option could be to override the DIE signal via $SIG{__DIE__},
although I don't know what consequences that would have in Plack...
I suspect a "catch all" won't be all that feasible.
--
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list
Koha-bugs@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
