Hey Alekto, I'm not sure what is going on in your project, but you
shouldn't have to change the TEMPLATE_DIRS setting.  I usually put themes
just before mezzanine.boot (they definitely need to be before
mezzanine.core.)   Are you using a default mezzanine-project created
settings file?  If so have you modified anything?  Particularly, what does
your TEMPLATE_LOADERS setting look like?

Does your project (not theme) have a templates folder?  If it does, and it
contains an index.html it will override your theme's index.html (by
default).  For example, in the following screenshot (of a project called
rail), if the highlighted folder templates (the project's templates folder)
had an index.html (it doesn't) it would override anything specified in the
templates folder of the app theme.
[image: Inline image 1]


On Mon, Dec 23, 2013 at 5:51 AM, Tom Lockhart <[email protected]>wrote:

>
> On 2013-12-21, at 3:32 PM, Stephen McDonald <[email protected]> wrote:
>
> > The app should be a proper Python package which in the least means it
> should contain an empty __init__.py file. At some stage Django required
> each app have at least an empty models.py module also, I'm not sure if
> that's still true.
>
> No, models.py is not required in an app for 1.5 (and pretty sure 1.4 also).
>
>                      - Tom
>
> --
> 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/groups/opt_out.
>

-- 
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/groups/opt_out.

<<Screen Shot 2013-12-23 at 10.54.00 AM.png>>

Reply via email to