On Sun, Jun 28, 2009 at 04:28:10PM -0700, Keith M. Corbett wrote: > > I'm seeing odd behavior after updating to the latest weblocks-dev. > I've been using weblocks-dev rev 1447 since early May, now I'm trying > to catch up. I ran into a few minor issues which were easy to hack > around. Now this problem has me stumped.
Are any of those minor issues worth fixing in upstream, or are they directly related to your application? > When I try to get a Weblocks application page an error is raised: > Unbound variable: HUNCHENTOOT:*SESSION* > > I see this running my own app, and also for the demos weblocks-demo > and weblocks-clsql-demo. What version of Weblocks are you using? The current tip, i.e. 1126/1d485a9? Do you run your app with cookies enabled? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
