Overview

Vestnik sends transactional email notifications for MODX 3. Emails go out in response to site events: sign-ups, orders, publishing, and your own events from templates and code.

Event → rule → recipients → template → queue → sending by cron → log.

How it works

1. An event happens on the site (sign-up, order, publishing, etc.).
2. Vestnik checks whether there are active rules for this event.
3. Recipients are determined for each rule. The template is rendered separately for each recipient — with the event data and the recipient data.
4. The finished email is put in the queue.
5. Cron processes the queue in batches and sends the emails; the result is written to the log.

There is no instant sending: all emails go through the queue and are sent only by cron. Without cron, no emails are sent.

Features

• Email templates with MODX tags: placeholders, filters, conditions; test sending from the manager.
• Four recipient strategies: administrator, event user, explicit addresses, MODX user group.
• Three event sources: a plugin for standard MODX events, the vestnik_notify snippet, the trigger() method in PHP.
• Retries on errors with growing delays, a log with resending, retention periods for email bodies and the log.
• Attachments from an allowed folder, a debug mode (all emails go to a test address).
• System events OnVestnikBeforeQueue, OnVestnikBeforeSend, OnVestnikAfterSend for your own plugins.

Manager page

Extras → Vestnik, tabs: Rules, Templates, Queue (with the “Process queue” button), Log, Documentation.