We just made a change to auth.navbar() so the login link is now treated like the other links. By default, the URL of the current page the user is on is added as a referrer to the query string of the login link (as well as all the other navbar links, except logout). After login, the user is automatically redirected back to the referring page. This was done to make login consistent with the other actions (register, profile, forgot password, etc.), as it wasn't clear why it should behave differently. You can also now override the referrer behavior for any or all of the navbar links. To limit the referrer behavior to a subset of links, just list them in the new referrer_actions argument:
auth.navbar(referrer_actions=['register', 'profile', ...]) To disable the referrers entirely, just set referrer_actions to None. If you exclude login from the referrer_actions list, then auth.settings.login_next will take effect. Anyway, why do you always want to redirect users to the profile page every time they log in? Are they expected to change their profile regularly? Anthony On Tuesday, July 10, 2012 10:51:28 AM UTC-4, Alec Taylor wrote: > > My routing broke between these two versions: > Version 2.00.0 (2012-06-18 17:07:27) dev > Version 2.00.0 (2012-07-10 00:22:32) dev > > So in my db.py I have a line: `auth.settings.login_next = > URL(f='profile')` > > Which is meant to redirect user to \profile\ once user is logged in. > Going to localhost.com\profile directly works. Logging in redirects me > back to the index page, but with the following appended: #_=_ > > Tiny test-case: https://gist.github.com/11f1119fac5799525b14 > > I can't think of anything else I've changed between upgrading to the > latest hg repo. > > How would you recommend I fix this issue? > > Thanks for all suggestions, > > Alec Taylor >
