Request-independent messaging for Django on top of contrib.messages
Project description
It’s almost like django.contrib.messages, but it doesn’t need request to message a user.
Implementation-wise, it’s a layer on top of Django’s contrib.messages.
To message a user you’ll simply create and save an instance of dbmessages’ Message model via shell, Django admin, or some other means.
Message model has, as fields, the attributes you’d normally pass to contrib.messages (level, message, extra_tags) plus a ForeignKey link to User model.
You’ll have to supply the addressee user yourself, this app doesn’t do any magic in that regard.
The next time given user appears on the site, middleware provided by dbmessages checks if user has any messages for them, and adds them to request using regular contrib.messages API. Then it deletes those messages from the DB. Simple as that.
Quick start
Make sure to enable Django’s contrib.messages in your project (check the docs).
Install django-dbmessages (it’s on PyPI).
Add 'dbmessages' to your INSTALLED_APPS and 'dbmessages.middleware.DBMessageMiddleware' to MIDDLEWARE_CLASSES.
Synchronize (or migrate) the DB.
Now you can get into shell and address a message to yourself:
>>> from dbmessages.models import Message >>> from django.contrib import messages >>> Message.objects.create(to_user=your_user, level=messages.INFO, message="Ahoy there")
Provided your front-end is integrated with Django’s contrib.messages, you should see the “Ahoy there” message the next time you log in under your account.
Changelog
0.2.0
Added Django-style initial migration, to support Django >=1.7.
Corrected check for Django version when choosing user model reference.
0.1.1
First stable release.
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.