Releases: loopwerk/django-generic-notifications
Releases · loopwerk/django-generic-notifications
1.3.0 (August 13, 2025)
New Features
- Include an absolute link to notification.url in the default emails
1.2.1 (August 13, 2025)
Bugfixes
- Fix pluralization issue in the digest emails (no more "1 new notifications")
1.2.0 (August 11, 2025)
New Features
- Add a proper apps.py file with a proper verbose_name
1.1.1 (August 4, 2025)
Bugfixes
- Prevent circular dependencies when your own models import our types
1.1.0 (August 3, 2025)
New Features
- Include user preference helpers with the library (#3 by kevinrenskers)
- Added helper methods to NotificationType (#4 by kevinrenskers)
1.0.0 (August 1, 2025)
This is a complete rewrite of django-generic-notifications. It keeps the same generic idea but much more flexible and modern. The last release was before Django even had migrations - it still used South!
- The NotificationEngine has been renamed to NotificationRegistry but behaves mostly the same.
- Backends have been renamed to channels, and we now ship with 2: website and email.
- Notification types work in much the same way, except for
allowed_backends
we now haverequired_channels
.
New features:
- The website channel means it's now very easy to show notifications on the website.
- Email digest with custom frequencies (daily, weekly).
- Notification grouping.
- Cleaned up and simplified. For example there's no more built-in queue, as it's not needed for the built-in channels. This allows people building custom channels to write their own processing functions that behave however they want.
- Unit tests 🎉
- Example project
0.2.2 (February 5, 2012)
- New timed queue, send notifications after a certain time
- The default types and backends are no longer registered by default, the developer needs to do this explicitly
0.2.1 (December 7, 2011)
- New model DisabledNotificationsTypeBackend: instead of saving what backend a user wants to use, we save what he does not want to use instead
0.2.0 (December 6, 2011)
- Define
__getattr__
for easy access to kwargs - Start of new settings app, where users can select which types they're interested in
- Users can also select backends per type
0.1.3 (December 5, 2011)
- Completely separated notification types and backends
- Rendered subject and text are saved in database queue
- Simpler to create notification, no more .do('add')
- New get_recipients method
- Able to set a different subject and/or text per different backend
- Respect FAIL_SILENT in _get_backends(self)
- Completely removed the Django messages backend (it didn't make sense)
- Updated docs and usage examples