search

johntynan / django-newsroom

Automatically exported from code.google.com/p/django-newsroom
Other
0 stars 0 forks source link

multiple sites support #22

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
We have talked about each affiliate/school publishing under their own 
subdomain, like 
asu.news21.com.  This would mean that every component in the system would have 
to be aware of 
what site it is part of or we use two separate installs to manage each site.  
The latter doesn't 
sounds like a good idea because of the necessary maintenance and I'm not sure 
how hard it would 
be to make things site-aware. If we want sites support should look into this 
sooner than later.

Original issue reported on code.google.com by mand...@gmail.com on 6 Apr 2009 at 1:25

GoogleCodeExporter commented 9 years ago

Original comment by mand...@gmail.com on 6 Apr 2009 at 1:28

GoogleCodeExporter commented 9 years ago

Original comment by jgty...@gmail.com on 13 Apr 2009 at 11:16

GoogleCodeExporter commented 9 years ago

Original comment by jgty...@gmail.com on 14 Apr 2009 at 1:16

GoogleCodeExporter commented 9 years ago 
Should We consider using django.contrib.sites.models as outlined here:

http://docs.djangoproject.com/en/dev/ref/contrib/sites/?from=olddocs#the-current
sitemanager

This will mean that we will need to add and additional property to our models:

sites = models.ManyToManyField(Site)

It may also have additional impacts down the road.

Original comment by jgty...@gmail.com on 14 Apr 2009 at 7:50

GoogleCodeExporter commented 9 years ago 
The answer to how to render projects should be in the ProjectsRFC ... which I 
will work on right now.

Original comment by mand...@gmail.com on 21 Apr 2009 at 1:02

GoogleCodeExporter commented 9 years ago 
This patch should implement the manytomany relationship between the Media and 
the sites.

Original comment by yann.ma...@gmail.com on 15 May 2009 at 2:21

Attachments:

GoogleCodeExporter commented 9 years ago 
Yann, since you have access to the repo can you just apply this?  I don't see 
much
that can go wrong, just test a bit.

Original comment by mand...@gmail.com on 15 May 2009 at 6:59

GoogleCodeExporter commented 9 years ago 
ok will do this.

Original comment by yann.ma...@gmail.com on 15 May 2009 at 8:44

GoogleCodeExporter commented 9 years ago 
Yann, actually it might be best to put this in a signal or in save() method of 
story?
Also we should do the same thing for propagating the status field.  So when a 
story
is published or unpublished all attached media is also updated?  On the other 
hand
maybe we should remove the status field from media.  If a piece of media is 
uploaded
it's available until removed... maybe it's just unecessary complication.

Original comment by mand...@gmail.com on 15 May 2009 at 9:01

GoogleCodeExporter commented 9 years ago

Original comment by yann.ma...@gmail.com on 15 May 2009 at 11:52