On Jan 4, 7:34 am, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> On Thu, 2008-01-03 at 23:10 +0530, venkata subramanian wrote:
> > Hi,
> > I had a problem recently.
> > To access the request object in all of my templates.
> > The solution I got surprised me. It involved explicitly passing o
Thanks a lot for your detailed answer.
In Zen terms, I am 'enlightened' now ;)
On Jan 4, 1:07 am, "Marty Alchin" <[EMAIL PROTECTED]> wrote:
> On Jan 3, 2008 2:33 PM, annacoder <[EMAIL PROTECTED]> wrote:
>
>
>
> > I understand *how* it is done.
>
> > But, my question was not related to the how pa
On Thu, 2008-01-03 at 23:10 +0530, venkata subramanian wrote:
> Hi,
> I had a problem recently.
> To access the request object in all of my templates.
> The solution I got surprised me. It involved explicitly passing on
> the request object from the views.
> (Example, to pass a RequestContext
On Jan 3, 2008 2:33 PM, annacoder <[EMAIL PROTECTED]> wrote:
>
> I understand *how* it is done.
>
> But, my question was not related to the how part.
Here's a quick rundown of the "why".
Templates aren't triggered by HTTP requests like views are. Instead,
they're rendered inside views, which *ar
I understand *how* it is done.
But, my question was not related to the how part.
On Jan 4, 12:17 am, Ariel Calzada <[EMAIL PROTECTED]> wrote:
> venkata subramanian wrote:
> > Hi,
> > I had a problem recently.
> > To access the request object in all of my templates.
> > The solution I got sur
Can you explain what is the security issue?
On Jan 3, 10:58 pm, Sam Lai <[EMAIL PROTECTED]> wrote:
> Security maybe?
>
> Not sure, but if you add django.core.context_processors.request to
> your TEMPLATE_CONTEXT_PROCESSORS list in settings.py, you won't have
> to explicitly add the request objec
venkata subramanian wrote:
> Hi,
> I had a problem recently.
> To access the request object in all of my templates.
> The solution I got surprised me. It involved explicitly passing on
> the request object from the views.
> (Example, to pass a RequestContext object as a context_instance
> para
No. RequestContext instance used to handle context processors. It
doesn't pass request instance to the context. Request instance passed
to template context only by "django.core.context_processors.request"
if its installed.
On 3 янв, 20:40, "venkata subramanian" <[EMAIL PROTECTED]>
wrote:
> Hi,
>
Security maybe?
Not sure, but if you add django.core.context_processors.request to
your TEMPLATE_CONTEXT_PROCESSORS list in settings.py, you won't have
to explicitly add the request object in every view. You still have to
pass a RequestContext object to the render_to_response method, but you
shou
Hi,
I had a problem recently.
To access the request object in all of my templates.
The solution I got surprised me. It involved explicitly passing on
the request object from the views.
(Example, to pass a RequestContext object as a context_instance
parameter in render_to_response method).
It
10 matches
Mail list logo
