Package: django-vox
Django vox is a django app that allow you to create and issue
different types of notifications. Notifications can have different
kinds of parameters which allow for convenient editing in the admin.FeaturesAdd and edit notifications from the adminBuilt-in message editor provides drop-down of available template variables
and supports previewingSupports many backends: email (html & text), SMS (Twilio), Twitter, Slack,
Postmark, XMPP, JSON webhooks, and Activity StreamsSupports attachmentsBuilt in site contacts that can be used to send emails to admins, or update
your organization‘s Twitter account, or send out webhooksFlexible API allows you to define your own user preferences about which user
gets which kind of notificationSet custom “from” addressesSend messages in bulk (all together) or individually customized messagesWhy this existsTLDR: Because I am lazy and I don’t want to spend my evening doing
a deploy just because marketing wants to update the text in their
latest spam mail.In a few more words:Editing copy for notifications shouldn’t have to be done by programmers.
This means:The notification templates should be editable in the adminThe information necessary to correctly make a template, whether
it’s a template ID or parameters) should be available in the admin
page. It shouldn’t be necessary to look through source code just to
make a notification work.Number 2 is actually a fairly difficult problem.People have different ways of interacting with computers, and one
way of doing notifications (i.e. email) doesn’t always make sense.Added to that, sending a text message that’s as verbose as an HTML
email is simply ridiculous. Each medium begets its own kind of
content.Since, as we mentioned earlier, content should be manageable
by non-programmers, the different ways of sending messages should
be manageable by non-programmers.I want it, stat!Well, why don’t you just head over tothe documentationand we’ll
get you started. A word of warning, it’s not super simple to setup, but
it’s worth it.CHANGES4.0.6Fix a bug where a contact could get the same notification twice4.0.5Fix another circular import dependency issue4.0.4Fix a potential circular import dependency issue4.0.3Fix a bug with get_recipient_choices ignoring the registered channels4.0.2Fix a bug when Notification.issue is passed SimpleLazyObject4.0.1Fix a bug withChannel.field4.0This version includes a new registration system for models so that you
don’t have to subclassVoxModel(which is a problem for 3rd party models).
The new way of registering the models is described in detail in the
documentation.Incompatibilities with Version 3:The actor & target arguments onNotification.issuemust be specified
by keyword arguments now. This doesn’t affectVoxModel.issue_notification, so it’s only relevant if you were manually
loading Notifications and triggering them.A few default backends were are no longer defaultsOther changes:Backend settings can just reference the class, and not the moduleNotify will use a default address if none is specifiedNotifications now have a “last updated” field3.6Fix bug in notification editor where switching one template’s backend would
alter the state of the another template form.Add more testsMakeBackend.send_messagean instance method, and instantiate backend
objects when sending messages. This is a significant API change, but it’s
unlikely to actually cause backwards compatibility issues.Add title to notify page3.5.3Fix bugs in demo caused by slugAdd icon3.5.2Add better support and testing for non-ID primary keys3.5.1Fix packaging problem (missing files)3.5Fix some javascript problems on Django 2.1 & 2.2Add one-time message admin actions3.4Fix crash when a non VoxModel model is registered3.3Pin to a newer version of august, it works much betterBe slightly more sophisticated with our activity data parsing3.2fix implementation of activity_type parameterFix bug issuing notifications with non VoxModel objectsFix bug where django will crash ifto_addressesis a generatorOmit skipping message when notification is not from codeFix bug where we kept recreating notificationsKeep orphaned notifications with templates so we don’t delete data3.1Add ability to remove notifications of deleted classesFix error in notification editor when using grappelli3.0Rewrite that add support for multiple participants2.3addread_atfield on inbox itemsUsers should be posting read activities to outbox, duh2.2Add the ability to post to inboxes and read messages2.1Redo activity schema so that its more straightforwardfix bug inbackground_taskimplementation2.0.0Add activity backend1.1.0Replace newlines in subject with spaceAdd support for resending failed messagesA few improvements to the adminAdd Grappelli compatibility1.0.0First stable release