MODX 3 component
Vestnik
Transactional email notifications for MODX 3: events, rules, templates, queue
12 pages2 sections12 min in total
Contents
01OverviewVestnik sends transactional email notifications for MODX 3. Emails go out in response to site events: sign-ups, orders, publishing, and your own…02Quick startOn the “Templates” tab click “New template”. MODX tags work in the subject and body: [[+username]], [[+email]], conditions via filters…
Event sources3
03vestnik.dispatcher pluginvestnik.dispatcher is installed with the component. It listens to the MODX system events it is attached to, turns their data into placeholders and…04vestnik_notify snippetQueues emails by the rules of your own event — for events that are not among the system ones. Call it uncached.05Calling from code (trigger)If the event happens in PHP (a payment handler, a plugin, a processor), queue the emails through the service:06Templates and dataThe template subject and body are rendered by the MODX parser: everything from &data (or the $data array) is available as [[+key]], and filters work.07Recipient strategiesA typical group use: “new order → email to all managers”. The email is rendered separately for each recipient — see Templates and data.08Queue, log and cronAll emails are queued; cron processes the queue in batches (vestnik_batch_size).09AttachmentsFiles are attached when calling from code: the reserved attachments key in $data is a list of paths on the server. It does not become a placeholder.10Settings and permissionsSystem Settings, namespace vestnik.