Great, guys! Solved! Now I have a global custom tag for recursive nested list in all the views! Nice! :-)
Next step: see if my hosting privider has python-memcache to put these guys under a cache... doesn't sound nice to have these repeated queries on a bank, considering they won't change so much... :-P Thanks for the help, guys! Thread solved! Diogo On Jul 5, 1:09 pm, diogobaeder <diogobae...@gmail.com> wrote: > Thanks, Yu, it was a lack of attention of mine, not just a typo... I > corrected the file name, now the module is being found, thanks! :-) > > Diogo > > On Jul 5, 6:32 am, Ronghui Yu <stone...@gmail.com> wrote: > > > _init_.py should be > > > __init__.py > > > or just a typo error in the mail? > > > diogobaeder ??: > > > > Koen, > > > > I tried to make an initial template tag, just to test and learn, but > > > it's not working. I followed the instructions here > > >http://docs.djangoproject.com/en/dev/howto/custom-template-tags/#howt... > > > and registered the compilation function, but it's not finding the > > > module, like stated here in this stack trace, even though I've saved > > > the _init_.py file: > > >http://dpaste.com/63306/ > > > > The code I used to test it is here: > > >http://dpaste.com/63308/ > > > > Any ideas? > > > > Thanks again! > > > > Diogo > > > > On Jul 3, 3:10 am, koenb <koen.bierm...@werk.belgie.be> wrote: > > > >> On 3 jul, 04:59, diogobaeder <diogobae...@gmail.com> 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 > > > -- > > Ronghui Yu <mailto:stone...@163.com> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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=en -~----------~----~----~----~------~----~------~--~---
