Package: django-inspectional-registration
AuthorAlisue <lambdalisue@hashnote.net>Supported python versions2.6, 2.7, 3.2, 3.3, 3.4, 3.5Supported django versions1.5 - 1.10django-inspectional-registration is a enhanced application ofdjango-registration. The following features are availableInspection steps for registration. You can accept or reject the account
registration before sending activation key to the user.Password will be filled in after the activation step to prevent that the
user forget them previously filled password in registration step (No
password filling in registration step)Password can be generated programatically and force to activate the
user. The generated password will be sent to the user by e-mail.Any Django models are available to use as supplemental information of
registration if the models are subclasses ofregistration.supplements.RegistrationSupplementBase.
It is commonly used for inspection.You can send any additional messages to the user in each steps
(acceptance, rejection and activation)The behaviors of the application are customizable with Backend feature.The E-mails or HTMLs are customizable with Django template system.Can be migrated fromdjango-registrationsimply bysouthdjango-mailercompatible.
Emails sent from the application will use django-mailer if ‘mailer’ is
in yourINSTALLED_APPSThe difference with django-registrationWhiledjango-registrationrequires 3 steps for registration,
django-inspectional-registration requires 5 steps and inspector for
registration.Online documentationSeedjango-inspectional-registration official documentsfor more detailFor translatorsTo create a message file, execute the following command (with your language)$pythonmanage.pymakemessages-ljaYou can compile the latest message files with the following command$pythonsetup.pycompile_messagesThe command above is automatically called beforesdistcommand if you callpython manage.py sdist.Backward incompatibilityBecause of anissue#24, django-inspectional-registration add the following three new options.REGISTRATION_DJANGO_AUTH_URLS_ENABLEIf it isFalse, django-inspectional-registration do not define the views of django.contrib.auth.
It is required to define these view manually. (Default:True)REGISTRATION_DJANGO_AUTH_URL_NAMES_PREFIXIt is used as a prefix string of view names of django.contrib.auth.
For backward compatibility, set this value to'auth_'. (Default:'')REGISTRATION_DJANGO_AUTH_URL_NAMES_SUFFIXIt is used as a suffix string of view names of django.contrib.auth.
For backward compatibility, set this value to''. (Default:'')This changes were introduced from version 0.4.0, to keep the backward compatibility, write the following in your settings module.REGISTRATION_DJANGO_AUTH_URLS_ENABLE=TrueREGISTRATION_DJANGO_AUTH_URL_NAMES_PREFIX='auth_'REGISTRATION_DJANGO_AUTH_URL_NAMES_SUFFIX=''Because of anissue#36, django-inspectional-registration add the following new option.REGISTRATION_USE_OBJECT_PERMISSIONIf it isTrue, django-inspectional-registration passobjtorequest.user.has_perminRegistrationAdmin.has_*_permission()methods. A default permission backend of Django does not support object permission thus it should beFalseif you don’t use extra permission backends such asdjango-permission.This change was introduced from version 0.4.7. To keep backward compatibility, write the following in your settings module.REGISTRATION_USE_OBJECT_PERMISSION=True