Base form classes¶
Several form classes are provided with django-registration, covering common cases for gathering account information and implementing common constraints for user registration. These forms were designed with django-registration’s built-in registration workflows in mind, but may also be useful in other situations.
A form for registering an account. This is a subclass of Django’s built-in
UserCreationForm, and has the following fields, all of which are required:
- The username to use for the new account.
- The email address to use for the new account.
- The password to use for the new account.
- The password to use for the new account, repeated to catch typos.
Validation of usernames
Django supplies a default regex-based validator for usernames in its base
AbstractBaseUserimplementation, allowing any word character along with the following set of additional characters: ., @, +, and -.
Because it’s a subclass of Django’s
RegistrationFormwill inherit the base validation defined by Django. It also applies some custom validators to the username:
Validation of email addresses
The HTML5 validator uses the HTML5 email-validation rule (as implemented on HTML’s input type=”email”), which is more restrictive than the email RFCs. The purpose of this validator is twofold: to match the behavior of HTML5, and to simplify django-registration’s other validators. The full RFC grammar for email addresses is enormously complex despite most of its features rarely if ever being used legitimately, so disallowing those features allows other validators to interact with a much simpler format, ensuring performance, reliability and safety.
Custom user models
If you are using a custom user model, you must subclass this form and tell it to use your custom user model instead of Django’s default user model. If you do not, django-registration will deliberately crash with an error message reminding you to do this. See the custom user compatibility guide for details.
Unicode case handling
This form will normalize the username value to form NFKC, matching Django’s default approach to Unicode normalization. it will then case fold the value, and use a case-insensitive (iexact) lookup to determine if a user with the same username already exists; the results of this query may depend on the quality of your database’s Unicode implementation, and on configuration details. The results may also be surprising to developers who are primarily used to English/ASCII text, as Unicode’s case rules can be quite complex.
A subclass of
RegistrationFormwhich adds one additional, required field:
- A checkbox indicating agreement to the site’s terms of service/user agreement.