I guess I misunderstood the problem. The point I was making is that you do not have to use auth methods to do things that it is not designed to do. You can make your own actions. Yet if you want to preserve names and urls, you may override existing methods.
On Jan 30, 2:56 pm, weheh <[email protected]> wrote: > I don't really understand why you would require a calss extension to > Auth when you can just have a separate table that points to the > auth_user table? The problem I know I'm going to run into is how to do > a self-submission on an Auth class where two tables are involved. How > am I going to deal with that? How do I prevent auth from taking over > and trying to do the self-submission itself? -- You received this message because you are subscribed to the Google Groups "web2py-users" 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/web2py?hl=en.
