Django-registration (redux) provides user registration functionality for Django websites.

This includes the changes required to implement a 3-step registration workflow.

1. User registers an account - is emailed with an activation token
2. User activates the account - site administrators are emailed in order to approve the user's newly created account
3. Administrators approve user's account - User is emailed and can now log in.

It contains a new registration backend which has been tested with all the previous tests and some newly added to test the new functionality.

For more information refer to the commit message. If the changes are not clear enough, I would be happy to provide documentation too. I have not done so yet as I would like some feedback first.

I am available to answer any possible questions. Thank you.

Checks for REGISTRATION_ADMINS defined in settings to use for the approval email instead of ADMINS. Triggers warning (about using ADMINS) if setting is not found

After upgrading from old django-registration to redux version my email template rendering blow up.

When I use django: loader.select_template(['registration/activation_email.txt']) I get the django-registration original template (while my overriden template is in my_app/templates/registration/activation_email.txt). The my_app/templates is discovered by AppDirectory template loader, it's on the django.template.loaders.app_directories.app_template_dirs folders list, but after "registration" app templates folder (as it's after "registration" on the INSTALLED_APPS lists).

select_template calls get_template which returns first match. For some reason it worked before, but now (Django 1.7.7 and @master django-registration-redux) it does not. I can hack it by providing dirs value (either filtered or reversed):

    from django.template.loaders.app_directories import app_template_dirs
    dirs = sorted(app_template_dirs, reverse=True)
    template = loader.select_template(['registration/activation_email.txt'], dirs=dirs)

But it would be good to know why and what is going on. It should "just work".

Documentation refer to installing https://django-registration.readthedocs.org/en/latest/quickstart.html

Using pip, type:

pip install django-registration

This is the original ubernostrum/django-registration, so this could be very confusing.

What about renaming your package? django-registration-ng or django-registration-macropin ?

Addresses #266, preventing the leaking of password reset token through the Referrer header.

For Django 1.11+, we fix by using the newer class based views.

For versions of Django below 1.11 we add a meta block to the template add at the meta tag <meta name="referrer" content="never">. In addition, we add rel="noreferrer" to the password reset email.

If I include urls with namespace

    url(r'^accounts/', include('registration.backends.simple.urls', namespace='registration')),

And use it like this in template

<li><a href="{% url 'registration:auth_login' %}">Login</a></li>

then it is not working in latest Django.

Just a heads up - (if not already fixed) but RequestSite is no longer in django.contrib.sites.models but is in django.contrib.sites.requests. I found that when I installed django-registration-redux, those old import statements are still there and I had to change them. If they are not changed, django throws import errors.

Thanks, @nnamdiee

Since it is already possible to use site for email notifications it would be great if it could be possible to override settings.DEFAULT_FROM_ADDRESS from function

Hey,

In a nutshell, as I added to the CHANGELOG:

• Feature: Added settings' options that allows to exlude the default auth urls (INCLUDE_AUTH_URLS) and register url (INCLUDE_REGISTER_URL).
• Feature: Added support to dynamically import any chosen registration form using the settings option REGISTRATION_FORM.
• Enhancement: Make RegistrationForm a subclass of Django's UserCreationForm
• Enhancement: Use registration form save method to create user instance, whenever form is a subclass of Django's ModelForm.

Basically I wanted to use your useful app in a project I'm working on, but with a few twists:

• I didn't want to use the register/ url, because I have two distinct profiles each one with a different register form and view.
• I wanted to use a registration form of my own, which is a subclass of ModelForm, with logic in the save method, associated with a custom user with no username field.

I've run the tests and everything is working. I've also updated the docs, version number and changelog.

Hope you approve my work. If you have any doubt, please contact me and I'll try to explain things better.

DLM

Hi,

I am not sure where to ask this, but I can't find anything on the internet. Did any of you had to use a two factor authentication with the registration module ? If yes, can you point me to some documentation or give me some info ?

Thanks a lot

I have the following settings -

REGISTRATION_OPEN = True # If True, users can register

ACCOUNT_ACTIVATION_DAYS = 7 # One-week activation window; you may, of course, use a different value.

REGISTRATION_AUTO_LOGIN = True # If True, the user will be automatically logged in.

LOGIN_REDIRECT_URL = '/' # The page you want users to arrive at after they successful log in

LOGIN_URL = '/accounts/login/' # The page users are directed to if they are not logged in, and are trying to access pages requiring authentication

INCLUDE_REGISTER_URL = True

And the following in the URLS -

... url(r'accounts/register/', BaseRegisterView.as_view(), name='registration_register'), (r'^accounts/', include('registration.backends.simple.urls')), ...

Following error -

Reverse for 'registration_activate' with arguments '('c6ae1dfec24759f7cd8013462c7240f0f21440aa',)'     and keyword arguments '{}' not found. 0 pattern(s) tried: []

Error during template rendering

In template /Users/Saket/.virtualenvs/oss/lib/python2.7/site-  packages/registration/templates/registration/activation_email.txt, error at line 13

Reverse for 'registration_activate' with arguments '('c6ae1dfec24759f7cd8013462c7240f0f21440aa',)' and keyword arguments '{}' not found. 0 pattern(s) tried: []
3   {% blocktrans with site_name=site.name %}
4   You (or someone pretending to be you) have asked to register an account at
5   {{ site_name }}.  If this wasn't you, please ignore this email
6   and your address will be removed from our records.
7   {% endblocktrans %}
8   {% blocktrans %}
9   To activate this account, please click the following link within the next

 10 {{ expiration_days }} days:
 11 {% endblocktrans %}

      http://{{site.domain}}
      {% url 'registration_activate' activation_key %}

Hi, forgive me if I'm not following the process. I'm new to github. This small change avoids a server hiccup is a user's name or email contains an illegal character (according to your DB).

Shouldn't the registration.models.RegistrationManager.activate_user send the user_activated signal? It would sure be helpful when writing my own unit tests...

Another think you might want to do is trigger a push to a contact management system (mailchimp, sendgrid or stripe for example) when a user is activated through the admin approval backend.

Using the Registration package prompts app_label issue when migrating from Django 1.8 to 1.11. The specific reason for this was that because of a custom user model which inherited from registration model. Hence this fix is to prevent such errors.

The maintainers of this project have discussed its future and agree that, in general, django-allauth is a better solution to Django User registration for those looking to adopt something.

However, we do not intend to stop maintaining this project. Our current goal is to continue supporting bug fixes, security fixes, enhancements, and new work from contributors, but to strongly suggest new adopters to look at django-allauth.

This is related to #181

django-allauth provides a more comprehensive solution to User registration and authentication than this project. Given the complexity of integrating different registration, authentication (two-factor, social auth, etc) with User management it generally makes sense to adopt one complete solution instead of combining many disparate solutions.

Ideally, django-registration should provide both code and documentation to move a Django project to django-allauth in a tested, repeatable way.