On 26/04/11 14:21, Madis wrote: > 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 site. > So the cookie for language just lives there and is only looked in if > there is no session available. It produces no overhead what so ever > because set_lang is only called when changing languages.
This does not address the fact that accessing the session to check causes a session to be created if it did not exist. This is what this whole thread is about! See also the discussion on ticket #13217. Luke -- "I washed a sock. Then I put it in the dryer. When I took it out, it was gone." (Steven Wright) Luke Plant || http://lukeplant.me.uk/ -- 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.
