Well we are actually not trying to address the issue on ticket #13217
I think. We are addressing the way language gets stored for the
client.
Because LocaleMiddleware checks for a session anyway. If it was
decided wontfix then doing it the way I supposed should be OK I think.
If I'm mistaken -
There is also a ticket here which proposes a patch -
http://code.djangoproject.com/ticket/14825
I used it last night - it also works but wont give the users the
freedom to choose if they want to set the lang cookie or not and also
adds overhead.
--
You received this message because you are
Well I think there is no need for another setting and I think there is
no problem setting the lang twice - as then the cookie is not always
accessed as it first checks for the language in the session. It only
looks for it in the cookie if there is no session or the customer is
returning to the
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
