Right now there are two possibilities: - if web2py redirects you to login, after login, login redirects you to the referencing page - if you go to the login page without redirection, after login, you go to login_next
I think what you see is consistent with this behavior. Am I wrong? Massimo On Jun 9, 2:36 am, annet <annet.verm...@gmail.com> wrote: > Massimo, > > r992 did not fix the login_next problem. > > In db.py I have: > > auth.settings.login_url=URL(r=request,c='authentication',f='login') > auth.settings.login_next=URL(r=request,c='core',f='index') > auth.settings.logout_next=URL(r=request,c='default',f='index') > > In 1.61.4 the first two worked, in 1.63.5 with r992 ... > > When on default/index, I choose login from the menu and login I am > redirected to default/index instead of core/index. > > When I expose a function from appadmin, I am redirected to login, when > I login I am redirected to:http://127.0.0.1:8000/admin/default/design/cms, > instead of core/index > > I also bookmarked the login page. When I login I am redirect to core/ > index. However, when I logout and login again, I am redirected to > default/index. > > So only when I login from outside web2py the login_next works > correctly. > > I am looking forward to a fix of this problem. > > Annet. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
