我目前有一个DetailView
用于Django的内置User
。
url(
r'^users/(?P<pk>\d+)/$',
DetailView.as_view(
model = User,
template_name = 'doors/users/detail.html'
),
name = 'users_detail'
)
但是当我在模板中访问user
时,它会显示当前登录的用户,而不是pk
用户从DetailUser
传来的用户}。我是否需要告诉DetailUser
将user
变量重命名为其他内容?如果是这样,我该怎么做?
答案 0 :(得分:12)
django.contrib.auth.context_processors.auth将{{ user }}
模板上下文变量设置为request.user或AnonymousUser。因此,它会覆盖由DetailView创建的{{ user }}
上下文变量:
def auth(request):
"""
Returns context variables required by apps that use Django's authentication
system.
If there is no 'user' attribute in the request, uses AnonymousUser (from
django.contrib.auth).
"""
# If we access request.user, request.session is accessed, which results in
# 'Vary: Cookie' being sent in every request that uses this context
# processor, which can easily be every request on a site if
# TEMPLATE_CONTEXT_PROCESSORS has this context processor added. This kills
# the ability to cache. So, we carefully ensure these attributes are lazy.
# We don't use django.utils.functional.lazy() for User, because that
# requires knowing the class of the object we want to proxy, which could
# break with custom auth backends. LazyObject is a less complete but more
# flexible solution that is a good enough wrapper for 'User'.
def get_user():
if hasattr(request, 'user'):
return request.user
else:
from django.contrib.auth.models import AnonymousUser
return AnonymousUser()
return {
'user': SimpleLazyObject(get_user),
'messages': messages.get_messages(request),
'perms': lazy(lambda: PermWrapper(get_user()), PermWrapper)(),
}
您可以setting context_object_name解决此问题。例如,这将启用{{ user_object }}
上下文变量,设置为DetailView的用户:
url(
r'^users/(?P<pk>\d+)/$',
DetailView.as_view(
model = User,
template_name = 'doors/users/detail.html',
context_object_name = 'user_object'
),
name = 'users_detail'
)
深入挖掘,阅读get_context_object_name()的文档。