If the links are static, you could just hardcode them into the base template. That would probably be a bit faster to do, but not as flexible as a tag would be.
~Jakob On Apr 6, 7:38 pm, Alex Gaynor <alex.gay...@gmail.com> wrote: > On Mon, Apr 6, 2009 at 11:54 AM, koranthala <koranth...@gmail.com> wrote: > > > Hi, > > I have many pages in my website - and all have the same default > > header and side bars. The header and sidebar contains ~15 links which > > are constant every time. While rendering templates for these pages, I > > always have to send all these links in the context. Since it is > > unseemly, I am planning to write my own context_processor for these > > headers. Now, I dont want the other template_context_processors to be > > hit for this - it seems a waste of time. Is it possible to go without > > hitting the other context_processors - since I would not have hit it > > otherwise. > > It's probably easier for you to just write a custom inclusion tag that > renders the nav. > > Alex > > -- > "I disapprove of what you say, but I will defend to the death your right to > say it." --Voltaire > "The people's good is the highest law."--Cicero --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
