Ticket #3483: authentication.profile-v2.diff

authentication.txt

@@ -1041 +1041 @@
                 return User.objects.get(pk=user_id)
             except User.DoesNotExist:
                 return None
+
+Extending the Profile system
+============================
+When it's necessary to build a website with users management, it's quite probable you need to collect some information about the users, for example, a telephone number, number of children, a picture...
+Django provides a lightweight way of defining a “profile” object that’s linked to a given user; this profile object can differ from project to project, and can even handle different profiles for different sites served from the same database.
+
+The first step in creating a profile is to define a model that holds the profile information. The model can be stored in any application, or just create a new one to manage the profile data.
+
+Let's create a new application. From console:
+        python manage.py startapp profile
+
+Now it's time to edit the models of the profile application. The only requirement Django places on this model is that it have a unique ForeignKey to the User model; this field must be named user Other that that, you can use any other fields you like. Here’s a strictly arbitrary profile model:
+
+from django.db import models
+from django.contrib.auth.models import User
+
+class MySiteProfile(models.Model):
+    # This is the only required field
+    user = models.ForeignKey(User, unique=True)
+
+    # The rest is completely up to you...
+    favorite_band = models.CharField(maxlength=100, blank=True)
+    favorite_cheese = models.CharField(maxlength=100, blank=True)
+    lucky_number = models.IntegerField()
+Next, you’ll need to tell Django where to look for this profile object. You do that by setting the AUTH_PROFILE_MODULE setting to the identifier for your model. So, if your model lives in an app called myapp, you’d put this in your settings file:
+
+        AUTH_PROFILE_MODULE = "myapp.mysiteprofile"
+in this case:
+        AUTH_PROFILE_MODULE = "profile.profile"
+Once that’s done, you can access a user’s profile by calling user.get_profile(). This function will raise a SiteProfileNotAvailable exception if AUTH_PROFILE_MODULE isn’t defined, and it also might raise a DoesNotExist exception if the user doesn’t have a profile already (you’ll usually catch that exception and create a new profile at that time).
+We add now the profile application to the INSTALLED_APPS in settings.py:
+INSTALLED_APPS = (
+        'django.contrib.auth',
+        'django.contrib.contenttypes',
+        'django.contrib.sessions',
+        'django.contrib.sites',
+        'django.contrib.admin',
+        'profile',
+        ...
+)
+It's time to create the table/s, from the console:
+        python manage.py syncdb
+To provide access to the profile, we add the next line to urls.py:
+        (r'^accounts/profile/$', 'profile.views.profile' ),
+And then, define the logic within /profile/views.py, this is a very simple example:
+        from django.http import HttpResponse
+        from django.template import RequestContext, loader
+        from django.contrib.auth.decorators import login_required
+
+        @login_required
+        def profile(request):
+                t = loader.get_template('accounts/profile.html')
+                c = RequestContext(request,{})
+                return HttpResponse(t.render(c))
+
+The content of the template depends of the data you want to show, and also the logic of the profile view. It would be easy to manage the data using the newforms library.
+This is a simple template to show basic data about the user (/templates/accounts/profile.html):
+        <p>This is the profile for the user {{ user.username }}. Last login:    {{ user.last_login|date:"l d \d\e F \d\e Y \a \l\a\s H:i:s"}}</p>
+        <p>Click here if you want to Logout: <a href="/cuentas/logout">Logout</a>       </p>
+As you can see, the profile it's easily yet powerful extensible.
+ Sin fin-de-línea al final del archivo