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 everything declared outsi
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 2
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
pr
If me, I would seperate those settings binding to domain from those not.
And create setting module for each domain.
Then in different virtual host configuration, just set setting module
pointing to different setting.py
Just my opinion, sorry if it doesn't work for you.
MS ??:
> Hi,
>
> I have a
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
dom
5 matches
Mail list logo
