alternative to {% if request.user.is_active %} in Django Templates

Question

What are the logic alternatives about:

{% if request.user.is_active %}

If the view doesn't return render_to_response with a dictionary with request, the template doesn't works properly.

So, any ideas are welcome.

//edited

my motivation is: when you work with views from installed apps, that you don't have the opportunity to modify them.

score 6 · Accepted Answer · answered Oct 10 '12 at 17:00

6

Add django.contrib.auth.context_processors.auth to TEMPLATE_CONTEXT_PROCESSORS in your settings.py.

Now your have user variable in all your templates. So you can use this:

{% if user.is_active %}

answered Oct 10 '12 at 17:00

defuz

`auth` is included by default, also could use `request` context processor which is not included by default. Furthermore, its better to note that `RequestContext` is required for the usage. – okm Oct 10 '12 at 18:00

Serhii Holinei · Answer 2 · 2012-10-10T16:59:09.943

view.py:

def foo_view(request):
    ...
    is_active = request.user.is_active
    return render_to_response('template.html', {'is_active':is_active})

or context_processor:

def is_user_active(request):
    return {'is_active': request.user.is_active}

or middleware:

class IsUserActive:
    def process_template_response(self, request, response):
        response.context['is_active'] = request.user.is_active

template.html:

{% if is_active %}
    ...
{% endif %}

But sincerely, I don't know why render_to_response does not satisfy you:

...
return render_to_response('template.html', 
    context_instance=RequestContext(request))

when you use some views from installed apps that you could not modify.for example: userena app, signin, signout views. — cleliodpaula, Oct 11 '12 at 00:38

2 Answers2