Scott L. Burson wrote: > In my case I have two navigation widgets, one with a "Log In" > selection, the second without it but with some additional selections. > There are two calls to REDIRECT needed. One goes in the :ON-CANCEL > action of the login. For the other, I have a "Log In" selection on > the second navigation which is declared to be hidden, and which > instead of an action has a function that does the REDIRECT with :DEFER > NIL. So when the second navigation is installed in the widget tree, > it receives the "log-in" URI token that is still hanging around, and > then forces the redirect. > > (Is this the "AJAX navigation issue" you're referring to, Leslie? It > doesn't seem to be AJAX-specific.)
Yes. The problem is not that the client has the wrong idea of the URI but that the server has no way in an AJAX request to get the current (last used) URI. So there can't be any dispatch. Therefore this problem will always show up when a navigation widget is inserted into or removed from the widget tree, unless it happens in a non-AJAX request. I've never needed to do this, actually. Can you come up with any situations where you really need to change the nav structure? Leslie -- 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.
