Hi, I find difficult to solve some recurring problems when developing my weblocks app. In particular, errors like 'odd number of &KEY arguments'.
Unfortunately, I don't know how to face the problem directly, instead of trial-and-error, commenting-uncommenting blocks, etc., until I find out where the error is. I don't know even if I can get the stack trace somewhere (even in the 500 error page). So I'm wondering if there's a way to 'mock' the request and session, so that I can call (make-instance) on widget classes directly from the REPL. I know in weblocks-test there's a (with-request) macro, but I wasn't able to use it so far. Am I missing something? Otherwise, I probably just need a way to continue from The variable HUNCHENTOOT:*SESSION* is unbound. [Condition of type UNBOUND-VARIABLE] 0: (WEBAPP-SESSION-VALUE WEBLOCKS::REQUEST-HOOKS)[:EXTERNAL] 1: (WEBLOCKS::SESSION-REQUEST-HOOKS) 2: ((SB-PCL::FAST-METHOD INITIALIZE-INSTANCE :AFTER (FLASH)) #<unavailable argument> #<unavailable argument> #<FLASH NIL>)[:EXTERNAL] Any ideas are welcome. Kind regards. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
