You are not the only person to have wasted a lot of time on this issue. There iso many issues that the Web2py team are excellent on, but this is not one of them.
'auth.navbar(referrer_actions=None)' Also did not work for me with 2.2.1 however putting 'auth.next = None' did work. In the battle of minds between Doug and Anthony, I had similar experience to Doug and tend to agree with him. (https://groups.google.com/forum/?fromgroups=#!topic/web2py/wKd5QN5R5fs) If setting auth.user.settings to a URL stopped the bit of code that generates _next when default/user/register is 'called' then it would seem to fit in with developers expectations. I am not sure why these ugly workarounds are necessary. The book still has this statment (when talking about setting auth.user.---_next) 'These must point to the URL you want to redirect your users to after the various possible auth actions (in case there is no referrer): ' This is an example of documentation that can only be understood by the person who wrote it, or other people who already know the answer. I expect everyone new to this expects setting auth.setting.register_next to a URL will cause the redirection. They all then find out the hard way it does not work. Trawl through the forums and try various things until coming up with a solution. I wonder how much time has been wasted on this (and the login_next etc). Peter > > --
