No no, the model will be served on all sites. Individual instances
will only be on a single site. So each site will have it's own set of
neighborhoods and locations. It's also possible that a neighborhood or
location will be on multiple sites.
The problem is that when dealing with a location in t
Let's break down exactly what you are trying to accomplish. You have a
model that you only want to be served only on a certain site. I
thought that flatpages was using a manager to figure this out, but if
actually applies a filter when flatpages is being fallen back on.
You can create a manager q
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
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 u
5 matches
Mail list logo
