Re: Django, multiple domains, multiple locales/languages

This could solve your problem domain based accounts. http://github.com/CrowdSense/django-muaccounts/tree/master On Jul 24, 3:57 pm, Joshua Russo wrote: > I ran into some conceptual problems with lazy vs non-lazy too. Any global > context needs to be lazy. This includes

Re: Django, multiple domains, multiple locales/languages

I ran into some conceptual problems with lazy vs non-lazy too. Any global context needs to be lazy. This includes everything declared outside of any function or class context and the class instance variable declarations (tho not the declarations made in __init__ or __new__ of a class) On Fri, Jul

Re: Django, multiple domains, multiple locales/languages

OK, thanks for suggestion - however it seems the problem was somewhere else - I was using ugettext where ugettext_lazy was supposed to be used (ex. in forms.py). The documentation should be more clear that the choice between ugettext and ugettext_lazy is quite important and may lead to strange

Django, multiple domains, multiple locales/languages

Hi, I have a problem with Django - I'm trying to build a website which will work on a couple of different domains and each domain should have a different language/locale. Example: domain.com -> English domain2.pl -> Polish The SITE_ID should change accordingly when I visit the corresponding