Those all are good ideas DR (especially the last resort pyc b/c I heard that screws things up once in awhile) and I will try them when I get home and update.
Really, any ideas helps. Thanks a ton! On Mar 18, 9:50 am, Daniel Roseman <[email protected]> wrote: > On Friday, March 18, 2011 4:35:12 PM UTC, Mazery Smith wrote: > > > Thanks for the response DR. > > > Isn't the "template tag library" already loaded in my example with > > this line: > > > {% load page_tags %} > > > My pagination_links tag is in the page_tags.py file. So that should > > work. Unless you are saying that the parent template (base.html that > > introContent.html extends) needs to have a load statement in it too. > > Is that what you are saying? > > > Just wondering b/c I don't really extract that meaning from the Djano > > docs here: > > >http://docs.djangoproject.com/en/dev/topics/templates/#custom-librari... > > """" > > When you load a custom tag or filter library, the tags/filters are > > only made available to the current template -- not any parent or child > > templates along the template-inheritance path. > > """ > > Sorry, my mistake: I didn't see the load tag (I always put them at the top > of the file after extends, so wasn't looking in the right place). Apologies, > you are right. > > My only suggestions are: are you sure page_tags actually does define the > "pagination_links" tag? Could there possibly be two page_tags templatetag > libraries? As a last resort, have you tried deleting the .pyc files in your > project (or just in your templatetags directory)? > -- > DR. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
