Re: django basic blog and inlines
doh! thanks Karen On Nov 16, 2:10 pm, Karen Traceywrote: > On Mon, Nov 16, 2009 at 1:58 PM, Bobby Roberts wrote: > > ok so i deleted what i had done and did the following: > > > 1. uploaded the entire basic app directory into django_apps/live/ > > basic > > 2. changed installed apps to load: > > basic.blog > > basic.inlines > > > Now i'm getting a totally different traceback > > athttp://www.thecigarcastle.com/blog/2009/nov/15/asdfasd/ > > > my installed apps does have django.contrib.comments > > > can someone decipher that and explain it to me? > > It looks like you have not done step 3 in the quick start to using comments: > > http://docs.djangoproject.com/en/dev/ref/contrib/comments/#quick-star... > > Karen -- 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=.
Re: django basic blog and inlines
On Mon, Nov 16, 2009 at 1:58 PM, Bobby Robertswrote: > ok so i deleted what i had done and did the following: > > 1. uploaded the entire basic app directory into django_apps/live/ > basic > 2. changed installed apps to load: > basic.blog > basic.inlines > > > Now i'm getting a totally different traceback > athttp://www.thecigarcastle.com/blog/2009/nov/15/asdfasd/ > > my installed apps does have django.contrib.comments > > can someone decipher that and explain it to me? > > It looks like you have not done step 3 in the quick start to using comments: http://docs.djangoproject.com/en/dev/ref/contrib/comments/#quick-start-guide Karen -- 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=.
Re: django basic blog and inlines
ok so i deleted what i had done and did the following: 1. uploaded the entire basic app directory into django_apps/live/ basic 2. changed installed apps to load: basic.blog basic.inlines Now i'm getting a totally different traceback athttp://www.thecigarcastle.com/blog/2009/nov/15/asdfasd/ my installed apps does have django.contrib.comments can someone decipher that and explain it to me? thanks in advance, -- 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=.
Re: django basic blog and inlines
On Mon, Nov 16, 2009 at 12:49 PM, Bobby Robertswrote: > Karen - > > Thanks for your reply... The path in both my blog and inlines module > was edited and i removed basic. from all the calls (since i wasn't > using the primary basic/ directory with all of the standard apps. The > error was there even if when i was using basic/blog or basic/inlines > structure as downloaded from the source. > > Mike - > > Thanks for your reply. The path to the inlines.py file is as follows: > > /django_apps/live/inlines/templatetags/inlines.py > > > OK so if you remove basic from both the import and the directory path, then you are left with an include, in that file above, that is: from inlines.parser import inlines ? Now the problem is you have two "inlines" modules (/django_apps/live/inlines/ and /django_apps/live/inlines/templatetags/inlines.py) and "from inlines.whatever" is ending up looking in the wrong place (the inlines.py file instead of the directory two levels up). (This is likely why the basic was included in the import in the first place.) I'd recommend returning the apps to their originally-coded state and using the structure they are assuming. Otherwise I do not know how much additional renaming you will need to do to to make things work properly. For this problem here you will need to rename one of the inlines modules (and update all imports that reference whichever one you decide to rename). Karen > > > On Nov 16, 12:33 pm, Mike Ramirez wrote: > > On Monday 16 November 2009 09:20:03 Bobby Roberts 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/ > > > > > > > The error i'm getting is: > > > > > > > 'inlines' is not a valid tag library: Could not load template > library > > > > > from django.templatetags.inlines, No module named parser > > > > > > > You can see the full traceback here: > > > > >http://www.thecigarcastle.com/blog/2009/nov/15/asdfasd/ > > > > > > > any ideas why this isn't working? > > > > > > > -- > > > > The inlines.py needs to live in your project/app/templatetags directory. > > > > I''m assuming live is your project,inlines is your apps, so something > like > > this: > > > > django_apps/live/inlines/templatetags/inline.py > > > > you should read this: > http://docs.djangoproject.com/en/dev/howto/custom-template-tags/#code... > > > > Mike > > > > -- > > He is no lawyer who cannot take two sides. > > > > signature.asc > > < 1KViewDownload > > -- > > 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=. > > > -- 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=.
Re: django basic blog and inlines
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 Robertswrote: > 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 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=.
Re: django basic blog and inlines
Karen - Thanks for your reply... The path in both my blog and inlines module was edited and i removed basic. from all the calls (since i wasn't using the primary basic/ directory with all of the standard apps. The error was there even if when i was using basic/blog or basic/inlines structure as downloaded from the source. Mike - Thanks for your reply. The path to the inlines.py file is as follows: /django_apps/live/inlines/templatetags/inlines.py On Nov 16, 12:33 pm, Mike Ramirezwrote: > On Monday 16 November 2009 09:20:03 Bobby Roberts 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/ > > > > > The error i'm getting is: > > > > > 'inlines' is not a valid tag library: Could not load template library > > > > from django.templatetags.inlines, No module named parser > > > > > You can see the full traceback here: > > > >http://www.thecigarcastle.com/blog/2009/nov/15/asdfasd/ > > > > > any ideas why this isn't working? > > > > > -- > > The inlines.py needs to live in your project/app/templatetags directory. > > I''m assuming live is your project,inlines is your apps, so something like > this: > > django_apps/live/inlines/templatetags/inline.py > > you should read > this:http://docs.djangoproject.com/en/dev/howto/custom-template-tags/#code... > > Mike > > -- > He is no lawyer who cannot take two sides. > > signature.asc > < 1KViewDownload -- 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=.
Re: django basic blog and inlines
On Monday 16 November 2009 09:20:03 Bobby Roberts 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/ > > > > > > > The error i'm getting is: > > > > > > 'inlines' is not a valid tag library: Could not load template library > > > from django.templatetags.inlines, No module named parser > > > > > > You can see the full traceback here: > > >http://www.thecigarcastle.com/blog/2009/nov/15/asdfasd/ > > > > > > any ideas why this isn't working? > > > > > > -- > > > The inlines.py needs to live in your project/app/templatetags directory. I''m assuming live is your project,inlines is your apps, so something like this: django_apps/live/inlines/templatetags/inline.py you should read this: http://docs.djangoproject.com/en/dev/howto/custom-template-tags/#code-layout Mike -- He is no lawyer who cannot take two sides. signature.asc Description: This is a digitally signed message part.
Re: django basic blog and inlines
On Mon, Nov 16, 2009 at 12:20 PM, Bobby Robertswrote: > 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. > > No, that's a red-herring error message. Django actually tries to load tag libraries from a templatetags directory under each app listed in INSTALLED_APPS. The fact that only django.templatetags is shown in the error message does not mean that inlines.templatetags wasn't tried. I think the problem is likely that you have removed the 'basic' element from the directory path for these apps. The blog one may not care, but it appears (I'm assuming you are using the basic apps from here: http://github.com/nathanborror/django-basic-apps) that the inlines one, as coded, requires that basic be part of the app path. See for example: http://github.com/nathanborror/django-basic-apps/blob/master/basic/inlines/templatetags/inlines.py#L2 Those imports include 'basic' in their path. If you have removed 'basic' from the path where they are actually installed those imports are not going to work any more. Karen -- 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=.
Re: django basic blog and inlines
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 Freemanwrote: > 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? > > Bill > > On Sun, Nov 15, 2009 at 10:34 PM, Bobby Roberts wrote: > > ok i have no idea what is going on here. I have django basic blog > > loaded to my site. I've also installed inlines as follows: > > > INSTALLED_APPS = ( > > ... > > 'inlines', > > 'blog', > > ) > > > (yeah i pulled out the blog dir from the basic dir because i'm not > > using all the other basic app stuff) > > > You can verify the blog is in fact working by going here: > >http://www.thecigarcastle.com/blog/ > > > Now click on the title to one of the posts: > > > The error i'm getting is: > > > 'inlines' is not a valid tag library: Could not load template library > > from django.templatetags.inlines, No module named parser > > > You can see the full traceback here: > >http://www.thecigarcastle.com/blog/2009/nov/15/asdfasd/ > > > any ideas why this isn't working? > > > -- > > > 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 > > athttp://groups.google.com/group/django-users?hl=. -- 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=.
Re: django basic blog and inlines
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? Bill On Sun, Nov 15, 2009 at 10:34 PM, Bobby Robertswrote: > ok i have no idea what is going on here. I have django basic blog > loaded to my site. I've also installed inlines as follows: > > INSTALLED_APPS = ( > ... > 'inlines', > 'blog', > ) > > (yeah i pulled out the blog dir from the basic dir because i'm not > using all the other basic app stuff) > > You can verify the blog is in fact working by going here: > http://www.thecigarcastle.com/blog/ > > Now click on the title to one of the posts: > > > The error i'm getting is: > > 'inlines' is not a valid tag library: Could not load template library > from django.templatetags.inlines, No module named parser > > > You can see the full traceback here: > http://www.thecigarcastle.com/blog/2009/nov/15/asdfasd/ > > > any ideas why this isn't working? > > -- > > 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=. > > > -- 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=.
django basic blog and inlines
ok i have no idea what is going on here. I have django basic blog loaded to my site. I've also installed inlines as follows: INSTALLED_APPS = ( ... 'inlines', 'blog', ) (yeah i pulled out the blog dir from the basic dir because i'm not using all the other basic app stuff) You can verify the blog is in fact working by going here: http://www.thecigarcastle.com/blog/ Now click on the title to one of the posts: The error i'm getting is: 'inlines' is not a valid tag library: Could not load template library from django.templatetags.inlines, No module named parser You can see the full traceback here: http://www.thecigarcastle.com/blog/2009/nov/15/asdfasd/ any ideas why this isn't working? -- 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=.