> > 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. >
Keep in mind, currently it is possible to enable referrers (i.e., the _next parameter in the URLs) while specifying a default redirect in case there is no referrer (i.e., via auth.settings.login_next). If we change the behavior, then we lose this capability and are limited to referrers only (with no default redirect) or a single fixed default only (with no referrers). So, we would be breaking backward compatibility and losing functionality. Instead, perhaps we can just improve the documentation. I don't think it's that complicated. Redirects from Auth pages are controlled via two methods: the _next parameter in the URL, and the auth.settings.[action]_next settings, with the former taking precedence. If you instead prefer the latter to take precedence, you just have to set the referrer_actions argument to auth.navbar() appropriately (or avoid using auth.navbar() altogether). Anthony --
