First version for Omeka Classic, the counterpart of the Announcements 1.1 module for Omeka S.
- Sending (Admins and Super Users): a title and a message in Omeka's TinyMCE editor, to everyone, to roles (Super, Admin, Contributor, Researcher) or to named users, or a mix; recipients are fixed when it is sent, inactive users never receive it, and sending is all or nothing.
- An inbox for every admin role, with Unread, All and Archived tabs and counts, Mark read or unread, Archive, Delete, Mark all read and Archive all; opening a message marks it read.
- The bell with the unread count next to the user's name, moved there by a few lines of script from Omeka's
admin_header_bottomhook (it stays in the header without script, and sits beside the menu button on phones), and an Announcements panel at the top of the dashboard. - Attachments: one uploaded file per announcement (documents, spreadsheets, slides, text, images, ZIP), stored through Omeka's file storage, so it works on local disk and with cloud storage such as Backblaze B2. The Omeka S module's Asset Library has no Classic counterpart.
- Links (http and https only) and expiry dates, entered in the site's time zone and stored in UTC.
- Email copies through Omeka's mail setup, from the Administrator Email, sent by a background job, each with a link to the recipient's own message; each user can turn them off at the bottom of their inbox.
- Recall: recipients see a notice, the message stops counting as unread, and email copies not yet sent are not sent.
- Cleanup of expired announcements, archiving or deleting their inbox messages: automatically a set number of days after expiry (checked at most hourly while the admin is in use, no cron), or at once with Run cleanup, which reports how many messages it changed.
- An announcement's page with every recipient and what they did with it (read and when, archived, deleted), who it was sent to, and delivery stats including the number of email copies sent.
- Safety: bodies are cleaned with HTML Purifier when sent and when shown, whatever the site's HTML Purifier setting, never in trusted mode; every button that changes something carries Omeka's session token; pages a role may not use give Omeka's Forbidden page.
- Sending, recall, cleanup and the settings are logged to the Audit Trail plugin when it is installed.