This could solve your problem domain based accounts. http://github.com/CrowdSense/django-muaccounts/tree/master
On Jul 24, 3:57 pm, Joshua Russo <josh.r.ru...@gmail.com> wrote: > 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 24, 2009 at 10:34 AM, MS <fretka1...@gmail.com> wrote: > > > 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 > > problems. > > > > 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. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
