Another more obscure possibility: I believe Django caches the available template directories (project's, and each app's) on startup - so if the server was up and running, and *then* you created the theme app, moving templates into it, all without restarting the server, the theme directory wouldn't be picked up until a restart - so try that.
On Mon, May 5, 2014 at 1:03 PM, Jared Nielsen <[email protected]>wrote: > Hi Stephen, > Thanks for your reply. > I've got my app, "theme", at the top of my INSTALLED_APPS. > > I'm guessing it's another setting. Could it have something to do with the > block just above INSTALLED_APPS? > > # Put strings here, like "/home/html/django_templates" > # or "C:/www/django/templates". > # Always use forward slashes, even on Windows. > # Don't forget to use absolute paths, not relative paths. > TEMPLATE_DIRS = (os.path.join(PROJECT_ROOT, "templates"),) > > > > On Sunday, May 4, 2014 6:52:13 PM UTC-6, Stephen McDonald wrote: > >> The ordering of INSTALLED_APPS matters when Django searches for templates >> to load: >> https://docs.djangoproject.com/en/1.6/ref/templates/api/# >> django.template.loaders.app_directories.Loader >> >> You'll see in Ross Laird's tutorial he includes "yourapp" at the top of >> INSTALLED_APPS. >> >> I suspect you've added your "theme" package to the end of INSTALLED_APPS, >> in which case the version found in "mezzanine.core" (listed earlier than >> "theme" in INSTALLED_APPS) would be loaded. >> >> >> On Mon, May 5, 2014 at 8:07 AM, Jared Nielsen <[email protected]>wrote: >> >>> I created a vanilla project and deployed it no problems, index.html/home >>> page render fine. On the server I ran collecttemplates and modified >>> index.html. The changes appeared. I then created an app, 'theme', moved >>> /templates into /theme, added it to my INSTALLED_APPS, synced the db, and >>> nothing. Back to stock home page. >>> >>> I'm following the customization instructions outlined by Ross on his >>> site: >>> http://rosslaird.com/blog/customizing-mezzanine/ >>> >>> Do my templates need to be in my project directory? And not in my theme >>> app? >>> >>> >>> >>> On Sunday, May 4, 2014 1:14:28 PM UTC-6, Jared Nielsen wrote: >>>> >>>> Just deployed with fabfile. Everything looks good except my home page. >>>> My index.html is not loading. >>>> My directory structure: >>>> >>>> /project: >>>> |-/portfolio >>>> |-/theme: >>>> |--/static >>>> |---/css >>>> |---/img >>>> |---/js >>>> |--/templates >>>> |---index.html >>>> |---/includes >>>> |---/pages >>>> |-manage.py >>>> etc. >>>> >>>> My static files and custom app templates are displaying properly. Just >>>> not my index.html. >>>> I read somewhere that it needs to be in /templates/pages, so I moved a >>>> copy there but no dice. >>>> >>>> More distressing, my home page is currently displaying an Error message >>>> followed by my nevercache key. >>>> >>>> Any help is greatly appreciated. >>>> Thanks. >>>> >>> -- >>> 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. >>> >> >> >> >> -- >> Stephen McDonald >> http://jupo.org >> > -- > 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. > -- Stephen McDonald http://jupo.org -- 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.
