Hi;

Short version: am trying to combine login widgetry with per-user
navigation.  My lazy protected navigation functions are getting called and
their HTML are being sent for the first user, but for the next different
user, while the functions to generate the new user's HTML are getting
called, the previous user's results are still sent back (as saved as
:selector children in the nav widget - boy was this tough to track down).
 Is there some canonical weblocks way to "reset" the session (widget tree,
etc.) after a logout?  Or should I be going about this entirely in some
other way (?user-id=12345 with an on-demand-selector)?

I am NOT using with-flow (googling the weblocks support group appeared to
argue against doing that), but using the login/protected-nav code from
here<http://paste.lisp.org/+2JQR/5>...
 The fact that this example code has the login widget living inside the
top-level nav makes it problematic to defer the creation of the top-level
nav (so as to be customized per-user) until after the authentication.  I
figure this has to be a well-understood weblocks problem with an equally
well-understood problem - sorry my Google/Lisp skills are not up to finding
it...

I did do the obvious thing of redirecting the non-privileged user to the
non-privileged page (worked fine), but the privileged page is still being
generated, and it's a simple matter to defeat the redirect by simply typing
in the privileged page URL.

FYI I am using quicklisp-load weblocks vintage weblocks-20110730-hg, which
differs from weblocks-dev (as fetched by hg) by only a few lines.  Platform
is Linux FC16 x86_64 running SBCL 1.0.46.40.

Thanks,

-jm

-- 
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.

Reply via email to