Django contrib.messages on steroids
Project description
Django contrib.messages on steroids
The app integrates smoothly with Django’s messages framework (django.contrib.messages), but users can decide which messages have to be stored on the database backend and kept available over sessions.
Features
Seamless integration with django.contrib.messages
All the features are in a mixin you can attach to your existing storage
Stored messages are archived in the database or in a Redis instance
Users can configure which message levels have to be persisted
REST api to retrieve and mark messages as read (needs djangorestframework being installed)
Requirements
Django 1.4/1.5/1.6
Python 2.7/3.3
Documentation
The full documentation is at http://django-stored-messages.rtfd.org.
Quickstart
Follow instruction for firing up django.contrib.messages, then install the app:
pip install django-stored-messages
Add it to the installed apps:
INSTALLED_APPS = ( # ... 'stored_messages', )
In the settings, tell Django which is the message storage:
MESSAGE_STORAGE = 'stored_messages.storage.PersistentStorage'
Then use it in a project through the django.contrib.messages api. The app provides for convenience some message levels which are persisted by default:
import stored_messages from django.contrib import messages # standard message messages.add_message(request, messages.INFO, 'Hello world.') # this will be persisted and marked as 'unread' messages.add_message(request, stored_messages.STORED_INFO, 'Hello world, to the database!')
stored_messages expose the same api as well, so one can do:
import stored_messages stored_messages.add_message(request, stored_messages.INFO, 'Hello!')
If you want to use standard message levels but persist the messages, just add something like this to the settings:
from django.contrib import messages STORED_MESSAGES = { # persist standard infos and standard errors 'STORE_LEVELS': (messages.INFO, messages.ERROR,), }
Iterating the messages will automatically mark them as read (but still persisted):
storage = messages.get_messages(request) for unread_message in storage: # unread_message could be a stored message or a "standard" Django message do_something_with(unread_message)
…unless you mark the storage as not used:
storage.used = False
You can mark a stored message as read at any time:
stored_messages.mark_read(request.user, message)
Want to store your messages on Redis instead of your database? Here you go:
STORED_MESSAGES = { 'STORAGE_BACKEND': 'stored_messages.backends.RedisBackend', 'REDIS_URL': 'redis://localhost:6379/0', }
Examples
GitHub-like notifications with Stored Messages and AngularJS
History
1.0.0 (2014-04-01)
New backend architecture with Redis support
Support for broadcast messages
0.2.1 (2013-12-23)
Added stored_messages_count template tag and tests
0.2.0 (2013-10-22)
Added stored_messages_archive template tag
Extended REST api
0.1.2 (2013-10-13)
Added specific template tags for stored messages
0.1.1 (2013-10-10)
Fixed setup.py
0.1.0 (2013-10-08)
First release on PyPI.
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
File details
Details for the file django-stored-messages-1.0.0.tar.gz
.
File metadata
- Download URL: django-stored-messages-1.0.0.tar.gz
- Upload date:
- Size: 13.6 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
File hashes
Algorithm | Hash digest | |
---|---|---|
SHA256 | 52fdeb3766335c8b9636da00575d78810f97d1072efd095bc3c62a325987169a |
|
MD5 | 27ca416cea34df9cb4d12d37e33547f4 |
|
BLAKE2b-256 | 41e94bdf3aafff96323b55008edd0461f35b92b80844ea6df197f0a8271216f8 |