I was using the context to directly get the GET request like: context[’urlinfo’], but it didn’t work after sending to a flatpage template, but thanks to you its works like a charm, and I can do this context[’request’].GET[’urlinfo’].

Thanks!

I’ve found that it’s very convinient to use a decorator writing simple line of code like @render_to(’mytemplate.html’) instead of passing RequestContext every time like context_instance=RequestContext(request) etc

Here is render_to decorator code. I’ve found it on internet, so I don’t know who is the author.
How to use it:
@render_to(’mytemplate.html’)
def myview(request):
return ({’parameter1: 1, ‘parameter2′:2})

Code:

from django.shortcuts import render_to_response
from django.template import RequestContext

def render_to(template):
“”"
Decorator for Django views that sends returned dict to render_to_response function
with given template and RequestContext as context instance.

If view doesn’t return dict then decorator simply returns output.
Additionally view can return two-tuple, which must contain dict as first
element and string with template name as second. This string will
override template name, given as parameter

Parameters:

- template: template name to use
“”"
def renderer(func):
def wrapper(request, *args, **kw):
output = func(request, *args, **kw)
if isinstance(output, (list, tuple)):
return render_to_response(output[1], output[0], RequestContext(request))
elif isinstance(output, dict):
return render_to_response(template, output, RequestContext(request))
return output
return wrapper
return renderer

(My original post was correct in the course of action to take, but poor in its language to explain it)

The context processor settings do not determine whether not the context is a RequestContext. This is determined by your view. If you’re using a generic view, then it will always be a RequestContext. But if you’re using render_to_response, you have to explicitly pass context_instance=RequestContext(request) as the third parameter.

If you do this, your context will be a RequestContext, even if you don’t add the Request context processor to your settings. Of course, if you don’t do that, you won’t have access to the ‘request’ in your template.