Notifications are short emails sent to users by Facebook or Twitter to inform users of some changes.
django-email-notification allows backoffice users to send short email notifications to django registered users or users you only know the email about what is new or changed from django’s admin or a dedicated view. And then track their clicks.
installation:
pip install django-email-notification
settings:
NOTIFICATION_TEMPLATE = 'email' # name of the templates to use (without extension). Must have a .txt and a .html version
NOTIFICATION_FROM_EMAIL = '' # sender email, typically no-reply@you-site.com
NOTIFICATION_FROM_NAME = '' # sender name
NOTIFICATION_UNSUBSCRIBE_REDIRECT = '/you-unsubscribed/' # possible page redirection after unsubscription
NOTIFICATION_REGISTRATION_MESSAGE_TAG = 'notification' # allow filtering notification messages
# Description of linkable objects.
NOTIFICATION_ASSOCIATED_OBJECTS = (
{ 'name': 'products', # reference name, used in forms and templates
'description': u"New products", # Human readable description
'long_description': u"Last products added to our site", # Long description
'class': 'project.application.models.Product', # path to the class model
'title_attr': 'product_description', # Model instance field or callable to display in form
'order_by': '-creation_date', # order to sort Model instances in form and email template
'manager': '', # manager to use if so
},
)
Email template:
In template, linked objects can be processed this way by example:
{% if object_types.OBJECT_NAME.instances %}
<ul><li>{{ object_types.OBJECT_NAME.long_description }}
<ul>{% for instance in object_types.OBJECT_NAME.instances %}
<li>{% include 'notification/emails/tracked_link.html' %}</li>
{% endfor %}</ul>
</li></ul>
{% endif %}
Messages sent through the django messages framework filtered like this:
{% if messages %}
{% for message in messages %}
{% if 'notification' in message.tags %}
<span class="email-registration-message lvl-{{ message.level }}">{{ message }}</span>
{% endif %}
{% endfor %}
{% endif %}
Metadata
Release files for django-email-notification 1.3
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 | |
|---|---|---|---|---|
| django-email-notification-1.3.tar.gz | 14.8 kB | Without provenance | Details |
Release files / django-email-notification-1.3.tar.gz
| Download URL | django-email-notification-1.3.tar.gz |
|---|---|
| Size | 14.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
de513653ba5b94770540bb57457fa1193c53d7e9569b2f1f1ad2be6490c7eee3
|
|
BLAKE2b-256 checksum How to use checksums |
7c009cd5c94029e15ef185b8b5c448afe32237b9e2f9b4fd23947b4dc622c430
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-email-notification 1.3
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.