[Seaside] Seaside 2.9: Seaside Walkback

[Julian Fitzell]

The trick being that in 2.9, you have to configure it on the
ExceptionFilter attached to the application rather than on the
application itself. If you go into the app's configuration, there is a
list of filters near the top and a link to configure them.

This is still one of the major pain points in the 2.9 alphas and is
holding us up from going to beta. It's basically a result of the tools
needing to be updated to hide what is, programmatically, a better
factoring of code but more complex to configure.

Julian

On Thu, Jul 30, 2009 at 9:08 AM, John Toohey<johnptoohey at gmail.com> wrote:
> Hi,
> You need to add the walkback or debug Exception handler to you app. In the
> Config UI for your app, click on Filters (config), and then select the
> Exception handler that you want in the General Settings. WADebugErrorHandler
> will start the debugger in your image, and WAWalkbackErrorHandler will give
> you the stack trace page.
>
>
> On Thu, Jul 30, 2009 at 00:13, Eric Hochmeister <erichochmeister at gmail.com>
> wrote:
>>
>> Hi,
>>
>> Is there something I need to setup in Seaside 2.9 to get a walkback?
>>
>> I am hitting a MNU message but I'm not getting a walkback or an option
>> to bring up the debugger.  What am I missing?
>>
>> All I see is a partially rendered page with the following displayed...
>>
>> "MessageNotUnderstood: UndefinedObject>>context
>>
>> Your request could not be completed. An exception occurred."
>>
>> Thanks,
>>
>> Eric
>> _______________________________________________
>> seaside mailing list
>> seaside at lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
>
>
> --
> -JT
>
>
>
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
>