In my case a unique base template per site is not necessary . A combination of refactoring out the base site/template at a much broader level - passing in the entire body from the child sites - and using includes in the child sites to keep the sites modular, seemed to do the trick. It looks like the base site template can easily be used for meta data and mezzanine settings.
Using the Django debug tool bar to get a visual on where the child site/templates were being inherited from made the task easier. Hope this helps someone. Cheers On Wednesday, August 27, 2014 at 10:51:16 PM UTC-7, Jesse Ramirez wrote: > > I'm trying to set up a project using multi tenancy. I've set up > HOST_THEMES correctly. > > The issue is each app has it's own base.html that's not being called. > Instead only the topmost app in INSTALLED_APPS's base.html is being called. > So all themes are extending a single base.html not their own. > > I would like each site to use it's own base.html. Is this possible? > -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
