I'm storing some additional per-user information using the AUTH_PROFILE_MODULE
.
We can access the user in a Django template using {{ request.user }}
but how do we access fields in the profile since the profile is only accessible via a function user.get_profile()
?
Is it really required to explicitly pass the profile into the template every time?
Use {{ request.user.get_profile.whatever }}
. Django's templating language automatically calls things that are callable - in this case, the .get_profile()
method.
Not sure why it's different for me, but I need to use {{user}} rather than {{request.user}}.
django.template.context_processors.request
inserts the request
in template, while the django.contrib.auth.context_processors.auth
inserts user
in context. docs.djangoproject.com/en/1.10/ref/templates/api/…
Yes it is possible to access profile from template using request.user.get_profile
However there is a small caveat: not all users will have profiles, which was in my case with admin users. So calling directly {{ request.user.get_profile.whatever }}
from the template will cause an error in such cases.
If you are sure all your users always have profiles it is safe to call from template, otherwise call get_profile()
from within try-except block in your view and pass it to the template.
{{ request.user.get_profile.whatever }}
, but {{ request.user.get_profile }}
will work and can be used to check whether a profile exists or not in current versions. See docs.djangoproject.com/en/dev/ref/templates/api/… . There is a note that that will change in the development version, though, see the paragraph above the one I linked to.
If it helps anyone, I used the followings in my template:
Username: {{ user.username }}
User Full name: {{ user.get_full_name }}
User Group: {{ user.groups.all.0 }}
Email: {{ user.email }}
Session Started at: {{ user.last_login }}
A sample result is like this:
User: auditor ezio User Group: auditGroup Username: testUser03 Email: testuser03@auditor.com Session Started at- April 16, 2018, 9:38 p.m.
Thanks :)
If you are using Django > 1.5 you can no longer use get_profile
.
If you have a legacy app, you should remove AUTH_PROFILE_MODULE = 'myapp.profile'
from your settings.py
.
If you use models.OneToOneField(User)
in your Profile class, you can simply use
{{ request.user.profile.whatever }}
in your Django template
request
keyboard in the front?
Working !
In your profile model provide related_name
user = models.OneToOneField(AUTH_USER_MODEL, related_name="user_profile", on_delete=models.CASCADE)
Then in template use. Here company_name is field in profile table
{{ request.user.user_profile.company_name }}
Success story sharing