Ok, if every site has its own settings.py file (and I think they have to,
since SITE_ID is a setting), then you could just have a different
TEMPLATE_DIRS setting for each site.

If you have two sites: store_a and store_b

store_a_settings.py
TEMPLATE_DIRS = (
    '/home/username/src/templates/store_a/',
    '/home/username/src/templates/generic/'
)

store_b_settings.py
TEMPLATE_DIRS = (
    '/home/username/src/templates/store_b/',
    '/home/username/src/templates/generic/'
)

http://docs.djangoproject.com/en/dev/ref/templates/api/#the-template-dirs-setting

That might accomplish what you are hoping for.

On Tue, Aug 25, 2009 at 7:31 PM, Ryan Headley <[email protected]>wrote:

>
> That's not a bad idea.  I must ask however if I am misinterpreting the
> point of the sites framework in django?  If someone wants to run
> multiple sites from one django instance is writing your own template
> loader the way to keep templates separate?  Just curious how others
> are handling this (satchmo or not)
>
> On 8/25/09, Alex Robbins <[email protected]> wrote:
> > If you really want the template looked up that way why not write your own
> > template loader? Just pull the source from one of the existing loaders
> but
> > don't look in so many places.
> >
> > http://docs.djangoproject.com/en/dev/ref/templates/api/#loader-types
> >
> >
> > On Tue, Aug 25, 2009 at 5:04 PM, Ryan Headley <[email protected]
> >wrote:
> >
> >> So its not as simple as just laying out a directory structure
> >> appropriately?
> >>
> >> Damn, here I was thinking I could have app1 find its templates in
> >> templates/app1 and app2 find its templates in app2, etc.
> >>
> >> I guess I had that impression from django itself -- *ugh*
> >>
> >> Thanks for the link, I'll take a look.
> >>
> >> Ryan
> >>
> >> On Tue, Aug 25, 2009 at 5:01 PM, Bruce Kroeze <[email protected]>
> wrote:
> >>
> >>>
> >>> On Tue, Aug 25, 2009 at 2:24 PM, lifewithryan<[email protected]>
> >>> wrote:
> >>> >
> >>> > I have a need to run the "Multi-Shop" functionality.  My question is,
> >>> > after reading some blog tutorials on GoSatchmo.com -- I think I have
> a
> >>> > directory structure like the one mentioned in the project layout
> >>> > tutorial:
> >>> >
> >>> > /estore -- this is my main directory with settings.py, urls.py etc.
> >>> >    /appname -- my custom app holding my custom product
> >>> >       __init__.py, models.py, etc
> >>> >    /templates -- my templates
> >>> >       /shop -- copied over from satchmo
> >>> >       /product -- copied over from satchmo
> >>> >
> >>> >
> >>> > My plan is that for my other "shops" i'll just add another "appname"
> >>> > directory like above.  Having said that, how do I ensure that my
> >>> > templates remain unique on a per-site basis? (Meaning StoreA
> shouldn't
> >>> > use the same templates as StoreB)
> >>>
> >>> You could use my "site-skins" module:
> >>> http://bitbucket.org/bkroeze/django-site-skins/
> >>>
> >>> --
> >>> Bruce Kroeze
> >>> http://www.ecomsmith.com
> >>> It's time to hammer your site into shape.
> >>>
> >>>
> >>>
> >>
> >>
> >> --
> >> http://www.sudovi.com/
> >> http://www.twitter.com/lifewithryan
> >> http://www.thecommontongue.com
> >> http://www.lifewithryan.com/
> >>
> >>
> >> >
> >>
> >
> > >
> >
>
> --
> Sent from my mobile device
>
> http://www.sudovi.com/
> http://www.twitter.com/lifewithryan
> http://www.thecommontongue.com
> http://www.lifewithryan.com/
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Satchmo users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/satchmo-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to