On Mon, 2008-12-15 at 23:54 -0800, redbaron wrote: > > > However, if you want to pass some extra information to the > > logout_then_login function, look at the third argument in the url() call > > -- the dictionary of extra parameters. You can set up the login_url > > parameter there. > > hardcoding login_url is not the way I prefer to go. I supposed there > is some solution to pass login_url dynamically, but it's impossible as > I can see.
This is a really simple problem: the URL tells you which view to call, and each different login_url value means essentially a different view, or at least a different parameter to pass to the same view. So either you need to put the variable information in the URL itself, or you need a different view each time that is a wrapper to call logout_then_login with the correct login_url parameter. Since each URL will be different in this second situation anyway, it's just a different version of case 1 -- perhaps the view has to convert the parameter in the URL to the real login_url value or something. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
