I'm not sure I understand how flatpages can help. I'm trying to limit what options show up in a select box in the admin interface so that if I have a Location on site A, when I go to select what Neighborhood it's in I'm only presented with the Neighborhoods that are also associated with site A and not the Neighborhoods from site B.
On Mar 26, 10:01 pm, Michael <[EMAIL PROTECTED]> wrote: > Django.contrib.flatpages does exactly what you are trying to > accomplish. It might be a bit of code to sort through but it is the > tried and true method to accomplish the multiple site one object idea. > > Hope that helps, > > Michael > > On Tue, Mar 25, 2008 at 1:47 PM, Josh <[EMAIL PROTECTED]> wrote: > > > I'm working on a multi-site project, so most models have a site field. > > One particular model, locations, has a site field as well as a many-to- > > many relationship with the neighborhood model which also has a site > > field. What I want is that when editing a location object the > > neighborhoods that show up in the select box are only those > > neighborhoods that are related to the same site as the location being > > edited. > > > It's been suggested that writing a custom manager might allow me to do > > this, but I'm at a bit of a loss as to how to start. Does anyone have > > any tips, or has anyone done somethign similar before? > > --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
