django-user-action-confirmation
===============================
Overview
~~~~~~~~
Easy and simple way to confirm user actions.
This one can be used with email or sms confirmation, but not provide this functional.
Installation
~~~~~~~~~~~~
Install developer version using PIP::
pip install -e git+https://github.com/alekam/django-user-action-confirmation#egg=user_action_confirmation
Change ``settings.py`` of your project. Add ``user_action_confirmation`` to
``INSTALLED_APPS``. Add required options (see: Settings).
Run ``manage.py syncdb`` or ``manage.py migrate options`` if you use South
and restart your project server.
Settings
~~~~~~~~
CONFIRMATION_OPERATION_CHOICES - required, list of tuples witch contains operation ID and short description
CONFIRMATION_MAX_DAYS - optional, default is 3 days
Usage
~~~~~
Install it, plug-in to your project and add required settings. Have fun!
Usage example (somethere in FormView.form_valid):
name = sa_setting('SOCIAL_AUTH_PARTIAL_PIPELINE_KEY',
'partial_pipeline')
backend = self.request.session[name]['backend']
email = form.cleaned_data['email']
token = Confirmation.objects.create(None, settings.OPERATION_REGISTER)
token.params = {
'email': email,
'backend': backend
}
token.save()
mail.send(
[email, ],
settings.DEFAULT_FROM_EMAIL,
template='confirm_registration',
context={
'user': {
'first_name': self.request.session.get('saved_first_name', '')
},
'site': Site.objects.get_current(),
'token': token.token,
'confirm_url': reverse('auth_confirm_email',
args=[token.token, ])
}
)
Provided template tags and libraries
~~~~~~~~~~~~~~~~~~~~~~~
No any templeate tags provided
Provided management commands
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
No any management commands provided
Testing
~~~~~~~
If this application is installed in your project you can run this inside your
project::
python manage.py test user_action_confirmation
or instead run inside this package::
python run_tests.py
Metadata
Release files for django-user-action-confirmation 0.1.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-user-action-confirmation-0.1.4.tar.gz | 5.2 kB | Without provenance | Details for django-user-action-confirmation-0.1.4.tar.gz |
Release files / django-user-action-confirmation-0.1.4.tar.gz
| Download URL | django-user-action-confirmation-0.1.4.tar.gz |
|---|---|
| Size | 5.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ea4d0ba7d0fdcf6fdb1ef662dc6969a2ded1a7e3a47b01d8f146ca4975d8a1a0
|
|
BLAKE2b-256 checksum How to use checksums |
26d26ca24a1fa6788127eabf7d8c20ab51dc94b47240d6043c61af2ab57821de
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-user-action-confirmation 0.1.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.