On Fri, Dec 5, 2008 at 4:12 AM, Kyle Fox <[EMAIL PROTECTED]> wrote: > > Thanks again. At this point I'm considering removing the Sites & > CurrentSiteManager from all of our apps entirely. Maybe I was overly- > optimistic about how Sites could be used; having to write a static > file just to get Sites/CurrentSiteManager working properly is > basically a deal-breaker.
We've done this for dynamic customer domains (lets call them "parties"): - ignore the sites app - have a middleware which looks at the request domain, and sees which party the request is for - it sets request.party with the Party model - then the view looks up/filters for the current party, via custom methods on the model managers - and request.party is made available in templates too. hth, Rob :) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
