[Seaside] Handling errors - staging/production

Sebastian Sastre sebastian at flowingconcept.com
Mon May 30 18:18:21 UTC 2011

Hey Francois,

for airflowing we did it like this:

server side works in two stages:

first (optimist case) a custom error handler clones the walkback of the exception and redirects the app to a custom error page (a tiny little very simple seaside app.) So, this page gives the user the option to write us about what was she doing or just click on "login again." In either case, the walkback reach us printed in an email along with the user who had the problem so we can provide support or notify her about an upgrade that had fixed the issue.

second, if things goes really bad, it falls back to a simple page saying that some less gentle error happened :)

and if the exception happens in the DOM side, it works like this:

the exception is captured in the onError handler and it reacts redirecting to the error page previously described.  Obviously this time we have no useful walkback but I've made it to print the component where that happened so at least I have something about the bug 



On May 30, 2011, at 2:41 PM, Francois Stephany wrote:

> What is the preferred way to handle errors on a production seaside application? Is there some kind of http://www.hoptoadapp.com/ to handle applications crashes/walkback?
> How do you typically do to handle errors?
> Cheers,
> Francois
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20110530/5a5e6130/attachment.htm

More information about the seaside mailing list