> > Nonetheless, how Auth implements where to go next just seems > excessively tangled. There are next parameters to the methods, next > parameters in the URLs, and finally, auth.settings.<something>_next > fields which are of the last resort, and it is hard to see under what > circumstances the auth.settings.<something>_next fields will ever get > used (except for login_next and logout_next, as per the code quoted > above). It would be nice to understand what the use case(s) are for > all these next 'control points'... >
Yes, I agree. At this point I still don't think I understand what's going on well > enough to submit a coherent bug report (I like to submit proposed > fixes too, but I'm not even close to thinking I can do that here). > I don't think it's a bug, per se, but the behavior (and documentation) could be improved. Anthony
