Thanks for the reply. I thought that might be the case but wanted to check.
There is a very good blogpost about this very topic at Liconln Loop http://lincolnloop.com/blog/2008/may/10/getting-requestcontext-your-templates/ but it was made last year and I hoped there was a setting we could change or set to make it global. Thanks again. On Jul 5, 5:23 am, Ronghui Yu <stone...@gmail.com> wrote: > I had the same problem. I didn't find a built-in way to solve this. But > I think you can implement a custom render_to_response, which calls the > built-in one in turn. > Then what you need to do is just importing your custome one. > > Streamweaver ??: > > > > > I'm still struggling a bit with template contexts > > > What I want to do is put a code snippet in the header of my site base > > template that either presents the user with a small login form if they > > aren't authenticated or display a "Welcome! user" where user is linked > > to their profile. > > > It seems I have to pass RequestContext(request) everytime I call > > render_to_response but I'm sure there's an easier way I'm missing. > > I've read through the docs and apologize if I'm missing it but can > > someone help with some advice? > > > Thanks in advance. > > -- > 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 -~----------~----~----~----~------~----~------~--~---
