Ahhh sorry I misunderstood stupidly what was being fixed =). That error page IS really nice.
On Mar 11, 3:52 am, "Leslie P. Polzer" <[email protected]> wrote: > On Mar 11, 11:42 am, Saikat Chakrabarti <[email protected]> wrote: > > > Robin, which error page are you referring to? > > The one that is supposed to show what Hunchentoot 1.0.0 took away. :) > > > Also using weblocks-dev, I can no longer do (setf > > hunchentoot:*catch-errors-p* nil) > > to redirect the hunchentoot errors to slime with a backtrace, and I've > > noticed that whenever I get any error at all in my app, I get a page > > saying > > > The function > > #<STANDARD-GENERIC-FUNCTION WEBLOCKS:HANDLE-ERROR-CONDITION (1)> > > requires at least 2 arguments. > > This should've been fixed after Robin's report above: > > 1390 391fb666d818 2009-03-11 09:29 +0100 polzer > fixed call to HANDLE-ERROR-CONDITION > > > How are you guys debugging errors in weblocks-dev? > > With the new error handler. :) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "weblocks" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/weblocks?hl=en -~----------~----~----~----~------~----~------~--~---
