Thanks, Anthony. I've tried it and it worked. I just passed an empty referrer_actions list.
The bahavior has changed for navbar since 1.99.7 though. In 1.99.7 login_next defined in db.py was not ignored. On Wed, Sep 12, 2012 at 2:03 PM, Anthony <abasta...@gmail.com> wrote: > That is by design. The _next variable in the URL takes precedence over > those settings, which are intended to be defaults. If you don't want the > navbar to include the _next variable, you can do: > > auth.navbar(..., referrer_actions=['list', 'of', 'actions']) > > Just make sure 'login' and 'register' are not in that list. > > Anthony > > > On Wednesday, September 12, 2012 2:39:11 AM UTC-4, Alexei Vinidiktov wrote: >> >> Hello, >> >> I have auth.settings.login_next and auth.settings.register_**next >> defined in db.py. >> >> Both appear to be ignored. >> >> I need the user to go to a specific page after he logs in or registers. >> >> In web2py 1.99.7 auth.settings.login_next defined in db.py was respected, >> auth.settings.register_next wasn't. >> >> Now neither is respected. The menus show the next links that point to the >> page that the user came from to the registration or log in page not the >> page that I want them to go to. >> >> -- >> Alexei Vinidiktov >> > -- > > > > -- Alexei Vinidiktov --
