So then the answer to my question is "no", you do not have a file inlines.py in a directory named "templatetags" which is itself in an app directrory recognizable by the presence of a models.py, the path such that the models.py file is importable as appname.models, and the app mentioned in INSTALLED_APPS. Since those are the only places the loader will look for the "inlines" tag library, it won't find one.
On Mon, Nov 16, 2009 at 12:20 PM, Bobby Roberts <tchend...@gmail.com> wrote: > the path to inlines.py is: > > /django_apps/live/inlines/inlines.py > > > live is on my pythonpath (my main application) > > blogs and inlines were pulled out of the basic app and put into these > directories > > /django_apps/live/blog/ (works) > /django_apps/inlines/ (doesn't work) > > you can view the full traceback here: > http://www.thecigarcastle.com/blog/2009/nov/15/asdfasd/ > > it's like it's trying to call inlines from > django.templatetags.inlines rather than from the inlines path noted > above. > > > > On Nov 16, 10:49 am, Bill Freeman <ke1g...@gmail.com> wrote: >> Do you have among your installed apps a name identifying a directory on the >> python path having both a models.py and a subdirectory named templatetags, >> that subdirectory containing a file inlines.py ? Or was that in the stuff >> you >> excluded from basic.app? -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=.
