Well yes I think there is an issue here for sure. I think it would be quite easy to solve this as follows - but I'm not sure if it's the best approach.
There is a setting named LANGUAGE_COOKIE_NAME which never gets used if you use session based cookies. The file cookie is just never saved. But if there were an option to save data in the session and also save the LANGUAGE_COOKIE as a file separately - then it would also persist after logout and solve the issue with languages after the session gets destroyed. http://code.djangoproject.com/ticket/14825 I think this middleware fix only fixes things temporarily - and in the long run you'd still want a persistent separate language cookie saved. I would propose to have the set_language() view with options to set it as a file based cookie or a session. https://github.com/django/django/blob/master/django/views/i18n.py It would allow the language file based cookie to have a very long expire date and the session would still be usable for storing secure data. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
