django-userprofiles
django-userprofiles is a simple registration app with some extra features.
Registration settings
- USERPROFILES_CHECK_UNIQUE_EMAIL
If enabled, the form checks if the user provided email is already in use. (useful if you want to allow user to log in with their email address)
- USERPROFILES_DOUBLE_CHECK_EMAIL
If enabled, the form shows two email fields. The user is required to enter the same email address twice.
- USERPROFILES_DOUBLE_CHECK_PASSWORD
If enabled, the form shows two password fields. The user is required to enter the same password twice to proceed.
- USERPROFILES_REGISTRATION_FULLNAME
If enabled, the registration form adds two fields for first and last name.
- USERPROFILES_REGISTRATION_FORM
You can override the default registration form by changing this setting. Defaults to ‘userprofiles.forms.RegistrationForm’.
- USERPROFILES_USE_ACCOUNT_VERIFICATION
This app provides a mechanism to verify user accounts by sending an email with an activation link. To use the account verification you have to add userprofiles.contrib.accountverification to your INSTALLED_APPS in order to enable the verification.
- USERPROFILES_ACCOUNT_VERIFICATION_DAYS
Defines the amount of days a user has to activate his account. Defaults to 7.
- USERPROFILES_EMAIL_ONLY
Removes the username field and generates a UUID for the required username for sites that want to use email addresses as logins.
- USERPROFILES_AUTO_LOGIN
Automatically log the user in upon registration. This setting cannot be used in conjunction with USERPROFILES_USE_ACCOUNT_VERIFICATION.
- USERPROFILES_REDIRECT_ON_REGISTRATION
Define a named URL to redirect the user upon successful registration. Defaults to ‘userprofiles_registration_complete’.
Profile settings
django-userprofiles is prepared to work with profile models and provides some features to make it easy to manage these profiles.
- USERPROFILES_USE_PROFILE
If enabled, userprofiles will look for the model set in AUTH_PROFILE_MODULE. it’s likely that you need to overwrite USERPROFILES_REGISTRATION_FORM to add your additional profile fields and define a save_profile method which is called after the user was created.
- USERPROFILES_INLINE_PROFILE_ADMIN
If enabled, userprofiles will add a profile inline to you user admin.
userprofiles.contrib.profiles
django-userprofiles also comes with a contrib app to allow profile changes and a profile view.
- USERPROFILES_PROFILE_FORM
You can overwrite the default profile form to add extra functionality. The default form is a ModelForm for you AUTH_PROFILE_MODULE.
- USERPROFILES_PROFILE_ALLOW_EMAIL_CHANGE
If enabled, the user is allowed to simply change the email address in the profile change view. This setting can only be activated if USERPROFILES_CHECK_UNIQUE_EMAIL is disabled.
If you want to check for unique emails and allow your users to change their email addresses, you have to use the emailverification app.
- USERPROFILES_PROFILE_CHANGE_DONE_URL
Defines the redirect destination after the profile was saved. Defaults to the named URL userprofiles_profile_change.
userprofiles.contrib.emailverification
django-userprofiles provides a simple app to do confirmed email address changes. (Users have the re-verify their email address after a change)
- USERPROFILES_USE_EMAIL_VERIFICATION
This app provides a mechanism to verify email changes by sending an email with an activation link. To use the email verification you have to add userprofiles.contrib.emailverification to your INSTALLED_APPS in order to enable the verification.
- USERPROFILES_EMAIL_VERIFICATION_DAYS
Defines the number of days a user has time to verify her/his new email address. Defaults to 2.
- USERPROFILES_EMAIL_VERIFICATION_DONE_URL
Defines the redirect destination after the email change was verified. Defaults to the named URL userprofiles_email_change.
Tools
There is an auth backend which allows your users to log in using their email address. Add userprofiles.auth_backends.EmailOrUsernameModelBackend to your settings if you want to use this feature.
Kudos to (the people who inspired me to write this code)
django-registration by James Bennett (https://bitbucket.org/ubernostrum/django-registration/)
to be continued.. If I used your code, send me a message! I’ll add you to this list.
Metadata
Release files for django-userprofiles 0.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| django-userprofiles-0.4.tar.gz | 20.2 kB | Without provenance | Details for django-userprofiles-0.4.tar.gz |
Release files / django-userprofiles-0.4.tar.gz
| Download URL | django-userprofiles-0.4.tar.gz |
|---|---|
| Size | 20.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
800d898a0033987d4b9aae00c91b158391939b84d4373eef87fd383b3df55533
|
|
BLAKE2b-256 checksum How to use checksums |
90bd89198cf62d0b8fc0554a35e82ecee04f43bb08690cb399d6f23ace9ac140
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-userprofiles 0.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.