[英]How to do a DetailView of Users in Django?
我目前有一個用於Django內置User
的DetailView
。
url(
r'^users/(?P<pk>\d+)/$',
DetailView.as_view(
model = User,
template_name = 'doors/users/detail.html'
),
name = 'users_detail'
)
但是當我在模板中訪問user
時,它會調出當前登錄的用戶,而不是具有我從DetailUser
傳遞的pk
的用戶。 我是否需要告訴DetailUser
將user
變量重命名為其他內容? 如果是這樣,我該怎么做?
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)(),
}
您可以通過設置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()的文檔。
聲明:本站的技術帖子網頁,遵循CC BY-SA 4.0協議,如果您需要轉載,請注明本站網址或者原文地址。任何問題請咨詢:yoyou2525@163.com.