You can do:
def user():
return dict(form = auth())
which looks in request.args[0] and exposes:
http://locahost:8000/application/default/user/register
http://locahost:8000/application/default/user/login
http://locahost:8000/application/default/user/logout
etc.
or
def register():
return dict(form = auth.register(next="login"))
def login():
return dict(form = auth.login(next="index"))
def logout():
return dict(form = auth.logout(next="login"))
which expose:
http://locahost:8000/application/default/register
http://locahost:8000/application/default//login
http://locahost:8000/application/default/logout
etc.
On Feb 12, 9:34 pm, blackthorne <francisco....@gmail.com> wrote:
> hi
>
> I just gave a try to the new Authentication scheme. Seems very easy
> and straight forward although I don't really understand how does it
> work behind the scenes.
>
> On the Authentication we have something like:
> def user():
> return dict(form = auth())
> in a controller that will generate lots of links
> like:http://locahost:8000/application/default/user/registerhttp://locahost:8000/application/default/user/loginhttp://locahost:8000/application/default/user/logout
> ...
>
> I feel very dumb at present moment since I can't understand the magic
> on the auth() to make this happen. I even gave a look at tools.py but
> I missed understanding what is going on.
> I was used to the model {application}/{controller}/{method}. Doesn't
> this break with it?
>
> More important than that...
> How can I generate, in a single page, both login and register forms
> since Auth() seems to generate them according the URL passed?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web2py Web Framework" group.
To post to this group, send email to web2py@googlegroups.com
To unsubscribe from this group, send email to
web2py+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---
