Comments on: How to get at request in a template http://www.willmer.com/kb/2008/12/how-to-get-at-request-in-a-template/ Sun, 15 Aug 2010 05:18:19 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Marc Remolt http://www.willmer.com/kb/2008/12/how-to-get-at-request-in-a-template/comment-page-1/#comment-32315 Marc Remolt Fri, 19 Dec 2008 12:45:44 +0000 http://www.willmer.com/kb/2008/12/how-to-get-at-request-in-a-template/#comment-32315 All generic views automatically use RequestContext, so with direct_to_template you can use {{ request }}. For render_to_response, you have to manually pass it to activate the context processors: ... return render_to_response('template.html', { my_context_as_dict }, context_instance = RequestContext(request)) All generic views automatically use RequestContext, so with direct_to_template you can use {{ request }}.

For render_to_response, you have to manually pass it to activate the context processors:
…
return render_to_response(‘template.html’, { my_context_as_dict }, context_instance = RequestContext(request))

]]> By: Rachel http://www.willmer.com/kb/2008/12/how-to-get-at-request-in-a-template/comment-page-1/#comment-32278 Rachel Thu, 18 Dec 2008 18:48:44 +0000 http://www.willmer.com/kb/2008/12/how-to-get-at-request-in-a-template/#comment-32278 This is referring to the case where you're just calling a template directly from the urls.py with 'direct_to_template' so no opportunity to do anything in the view. I hadn't made that clear, thanks, I've added a wee note on that. This is referring to the case where you’re just calling a template directly from the urls.py with ‘direct_to_template’ so no opportunity to do anything in the view.

I hadn’t made that clear, thanks, I’ve added a wee note on that.

]]> By: Enrico http://www.willmer.com/kb/2008/12/how-to-get-at-request-in-a-template/comment-page-1/#comment-32277 Enrico Thu, 18 Dec 2008 18:29:15 +0000 http://www.willmer.com/kb/2008/12/how-to-get-at-request-in-a-template/#comment-32277 I think you forgot, you need to use RequestContext in your view in order to get the request available in the template. That's because the request isn't globally available. Check this page: http://www.b-list.org/weblog/2006/jun/14/django-tips-template-context-processors/ I think you forgot, you need to use RequestContext in your view in order to get the request available in the template.

That’s because the request isn’t globally available.

Check this page:
http://www.b-list.org/weblog/2006/jun/14/django-tips-template-context-processors/

]]> By: Peter http://www.willmer.com/kb/2008/12/how-to-get-at-request-in-a-template/comment-page-1/#comment-32275 Peter Thu, 18 Dec 2008 17:35:28 +0000 http://www.willmer.com/kb/2008/12/how-to-get-at-request-in-a-template/#comment-32275 If you really need to access request across multiple views, it's smarter to use the context processor. If you really need to access request across multiple views, it’s smarter to use the context processor.

]]> By: Erik http://www.willmer.com/kb/2008/12/how-to-get-at-request-in-a-template/comment-page-1/#comment-32274 Erik Thu, 18 Dec 2008 17:08:14 +0000 http://www.willmer.com/kb/2008/12/how-to-get-at-request-in-a-template/#comment-32274 Django noob here: is this any better or worse then simply passing along request from the view? Django noob here: is this any better or worse then simply passing along request from the view?

]]>