Okay, I get it now. Adding ":use-ajax-p nil" to the login view stopped the JS dialog box, but still resulted in the standard Weblocks error page, which is what's displayed after coming back to a pre-existing session. So it is one issue, it just shows up in a couple of different places.
FWIW, a redirect accomplishes pretty much the same thing as :use-ajax-p nil, but in a messier way. So it looks like the only way to have protected selectors is to, well, implement protected selectors. Unless you've got any better ideas, I'm going to go ahead and do that with the help of those previous posts. Thanks for all the help you've provided so far. -- 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.
