Great, koenb, now its getting even clearer to me! :-) Thanks for the light,
Diogo On Jul 3, 3:10 am, koenb <[email protected]> wrote: > On 3 jul, 04:59, diogobaeder <[email protected]> wrote: > > > But where do I put the custom template, than? If I load it from an app > > template, I must create it under <app>/templatetags/, and what if I > > want to call it from the base template? <project_root>/templatetags/? > > > Thanks! > > > Diogo > > I think you are missing something here: there really is no app > namespacing in templatetags: if you try to load a tag library, django > will search the templatetags folders located underneath all installed > apps. If it finds one that matches, it will use that one. This means > that you can use a tag library from app X in any template you use (no > matter where it is located), as long as app X is in the installed > apps. The downside of this is that you need to name your tag libraries > wisely, because tags.py in app X and tags.py in app Y will conflict. > > Koen --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
