Oh duh, I moved TEMPLATE_DIRS to my local_settings.py and didn't see it at first. That makes sense why this wasn't working now. Thanks.
On Monday, August 10, 2015 at 3:18:06 PM UTC-5, David Hoese wrote: > > Hi Eduardo, > > I think that makes sense. I haven't done a lot of custom templating and > CSS in my project so far, but from what I saw in Josh's blog post it > made it look like the project application should be treated like an > application, but with settings.py and other project level files. > > I did get it to work by listing my project application as one of the > INSTALLED_APPS on my development machine, but I'm not sure if that is > intended. I guess I'll just do the "theme" app if I don't hear anythign > else. Thanks. > > -Dave > > On 8/10/15 2:38 PM, Eduardo Rivas wrote: > > You have two options: > > > > - Use the the top-level "templates" directory defined in settings.py > > > https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/project_template/project_name/settings.py#L199. > > > > You can also change this to whatever path you like. > > > > - You can create a "theme" app and put templates there. They will be > > picked up by Django simply because it's a regular application added to > > INSTALLED_APPS. > > > > As far a I know, nothing has changed in this regard from Mezzanine 3 to > 4. > > > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
