After much tinkering with modal login, I'm formulating the following opinions: - modal login is a powerful and useful capability - modal login is not well supported by web2py and not at all a functionality that newbies would be able to implement easily. As per pbreit in http://groups.google.com/group/web2py/browse_thread/thread/1394315562b1bba0/729729e02bdba61f#729729e02bdba61f, if you use modal login you run into troubles elsewhere when you need to point to a login url. For instance, if you decorate with @auth.requires_login(), then you're going to run into trouble. That's because you'll be redirected to a login page, which doesn't exist. - the implementation of auth does not natively support components. This requires a workaround -- intercepting the login completion with auth.settings.login_onaccept and raising an HTTP call. However, it seems as though _onaccept is not uniformly implemented throughout auth.
I believe an experienced user can workaround these issues. However, with the rise of components and jQuery interactivity, I think it's in the community's interest to revisit auth and see how it can be improved to support these new web2py and jQuery capabilities. What do you think?
