I've been playing with it a little today and it appears to be perfect
for what I was looking for.
I need to build a couple of websites (may expand out to more in the
future) which will be sharing a quite a few stories with a common
administrator. so after fiddling with it a little bit and setting up a
manytomany join from the stories to the sites I'm now able to show the
same story on multiple sites while still being able to control which
sites it displays on.
Below is some code which I mostly worked out by looking into flatfiles
and working out how to get my stories to use the functionality.
--- model ---
from django.core import meta
from django.models.core import Site
class Story(meta.Model):
fields = (
meta.CharField('title', 'Story Title', maxlength=200),
meta.TextField('body', 'Story Content'),
meta.CharField('author', 'Author', maxlength=200, blank=True),
meta.CharField('location', 'Country/Location', maxlength=200,
blank=True),
meta.CharField('keywords', 'Keywords', maxlength=200,
blank=True, help_text="Keywords separated by comma's"),
meta.DateTimeField('pub_date', 'Date Published', auto_now_add=True),
meta.BooleanField('active'),
meta.ManyToManyField(Site),
)
............
--- view ---
............
latest_stories_list = storys.get_list(order_by=['-pub_date'], limit=5,
active__exact=1, sites__domain__exact=DOMAIN)
............
Currently I'm hardcoding DOMAIN, though plan to pull it in from the
http headers.
On 8/18/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> This ``sites'' thing seems useful to me, but I don't quite understand
> how I might use it. I can't find any documentation for it, so I get
> the feeling it may be deprecated.
