[Seaside] 'Allow debugging of errors' does not work for rendering? Only for callbacks?

Lukas Renggli renggli at gmail.com
Mon Feb 7 16:33:44 UTC 2011

That would be a cool setting indeed, but it is currently not implemented.


On Monday, 7 February 2011, James Foster <Smalltalk at jgfoster.net> wrote:
> Is there a way to configure Seaside so that an error during rendering will be reported to the client browser with a walkback (as we had in Seaside 2.8)?
> I am using the Seaside 3.0.3 One-Click Experience Pharo download and on the Configure page from the Welcome page I've checked the 'Allow debugging of errors' checkbox. When I have an error during a callback, the error is reported properly. When I have an error during rendering, a walkback happens in Smalltalk with the error that a call is not allowed here.
> renderContentOn: html
>         html headingg: model.   "this error does not behave the way I want"
>         html anchor
>                 callback: [self foo];   "this error is presented in the web browser as a walkback"
>                 with: 'click me!'
> James_______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

Lukas Renggli

More information about the seaside mailing list