StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
4411999
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-12-10T18:22:56.187
FavoriteCount
0
LastActivityDate
2010-12-10T18:31:58.157
LastEditDate
2010-12-10T18:31:58.157
LastEditorUserId
255918
OwnerUserId
255918
ParentId
4411924
PostTypeId
2
Score
5
ViewCount
0
LastEditorDisplayName
text
Body
django-registration allows you to write a <a href="http://docs.b-list.org/django-registration/0.8/backend-api.html">custom backend</a> to handle custom activation needs. So what you'd do is create your own backend, implementing the <code>register</code> and <code>activate</code> yourself. Here's an example of how you could implement the <code>register</code> function: <pre><code>def register(self, request, **kwargs): username, email, password = kwargs['username'], kwargs['email'], kwargs['password1'] if Site._meta.installed: site = Site.objects.get_current() else: site = RequestSite(request) new_user = RegistrationProfile.objects.create_inactive_user(username, email, password, site, send_email=False) # send an email to the admins with user information send_new_user_notification(new_user) # you would write this function signals.user_registered.send(sender=self.__class__, user=new_user, request=request) return new_user </code></pre> The key point is to make sure <code>send_email</code> is set to false; that will prevent the user from getting an activation link. Then you can decide whether the email sent to the admins has an activation link or if you're content with them going to admin and just checking the "Active" box. If you use <code>AuthenticationForm</code> from <code>django.contrib.auth</code> then it will automatically reject users whose <code>is_active</code> is False, but if you're not using that then make sure to run the following check for any request where an active user is required: <pre><code>def restricted_view(request): if request.user and request.user.is_active: #continue with the code </code></pre> You can also write your own decorator (look at <code>@login_required</code> for pointers). Note that <code>@login_required</code> does not check for <code>is_active</code>. 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to set-up django-registration that an account needs to be manually activated?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USJordan Reiter
UserOwnerUserId
1. USJordan Reiter
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow to set-up django-registration that an account needs to be manually activated?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.