Version 5.3.1
November 8, 2026
Security
- The front-end script reads
data-yo-site-configonly from<html>or<body>. It used to take the first one anywhere in the page, so an attribute that survived a sanitiser in user content could replace the page's config — including, on the injected path, the visitor's CSRF token, which stopped every message button and dismissal working. Put{{ craft.yo.runtimeConfig() }}on<html>or<body>; anywhere else it is now ignored. - The script only fetches the CSRF token from, and only sends it to, the page's own origin. A
sessionInfoUrlfrom the page or fromwindow.YoSiteConfigthat points elsewhere is dropped, and adata-yo-postor dismiss URL on another origin is not posted to. Options passed toYoSite.start()are trusted as before. - A
window.YoSiteConfigthat is not a plain object — an element named by anidin user content — is ignored rather than read as config.
Version 5.3.0
November 8, 2026
Added
- The front-end script can be bundled with your own JavaScript instead of loaded from Craft's
asset URL. Turn off Load the front-end script for me, import
yo-site.mjs(ES modules) oryo-site.js(CommonJS or a plain script), add{{ craft.yo.runtimeConfig() }}to the page and callYoSite.start(). With no arguments it reads the class prefix and the auto-dismiss delay from the page, so they still follow Yo's settings; the visitor's CSRF token is fetched fromusers/session-inforather than written into the page, so the page stays cacheable. - A DataStar alias setting, for a bundled script on a site that already runs DataStar 1.0:
Yo's front-end markup is written for that DataStar (
data-on:click, or your build's alias) instead of for Yo's own aliased copy, so the page never needs two. window.YoSite, withstart(). Loading the script twice — injected and bundled — leaves one instance.
Changed
- The default front-end template writes its DataStar attributes as
{{ ds }}on:click. An overriddenyo/_messages.twigthat hard-codesdata-yo-ds-on:clickkeeps working while Yo loads the script itself. - The injected
window.YoSiteConfigalso carriessessionInfoUrl.
Version 5.2.0
October 9, 2026
Added
- An email channel: messages go to the inboxes of the people they are addressed to — a group's
members, one user, or for
everyone, everyone who can reach the control panel. One email per message (queued), or a daily or weekly digest per person, run byphp craft yo/digest/sendon cron with a web-request fallback.yo/digest/statusshows the schedule and what is waiting. - A webhook channel: Slack, Microsoft Teams or plain JSON, to one admin-set URL (
$ENVsupported), optionally HMAC-signed withX-Yo-Timestamp/X-Yo-Signature. Posts are queued and retried, and go through the family's SSRF guard — public addresses only, pinned at connect time, no redirects. - A per-type routing table for both ("errors and warnings to email, errors to Slack"). It applies to messages addressed beyond the current request; a plugin can also ask for either channel by name.
- "Send a test email" and "Send a test post" buttons in the settings, admin-only and using the saved settings.
Email::EVENT_BEFORE_SENDandWebhooks::EVENT_BEFORE_POST, to change or cancel what goes out.
Changed
- Two new tables,
yo_email_queueandyo_digests, for the email digest. Runphp craft up.
Version 5.1.0
September 29, 2026
Fixed
- Yo no longer breaks other markup on the page. DataStar is now scoped to
data-yo-ds-*attributes; before, it evaluated Craft's owndata-attrtable cells as JavaScript and loggedReferenceError: … is not definedon every control panel element index. - The panel's DataStar click handlers (open/close, move, clear all, message actions, the settings
test buttons) now run — they used pre-1.0
data-on-clicksyntax, which DataStar 1.0 ignores. - The front-end channel's first poll on page load now fires (
data-on-load→data-init).
Version 5.0.0
August 27, 2026
Initial release.
Added
- A message bus with one API for every plugin on the site:
Yo::success(),Yo::error()and a fluent builder for everything else. - Five message types — success, notice, tip, warning, error — each with its own colour, icon,
stickiness and sort priority, and
Types::EVENT_REGISTER_MESSAGE_TYPESfor plugins that want their own. - Three channels — the control panel, the front end and the Craft log — and
Channels::EVENT_REGISTER_CHANNELSfor plugins that want to add a fourth. - Receipts: shown, read, dismissed and actioned, each an event carrying the sending plugin's own context back to it.
- Audiences: the current user, one user, a user group, or everybody. Broadcasts cost one row.
- A floating control panel panel, positionable to any of six anchors by dragging or from a menu, remembered per person.
- A dashboard widget listing what is waiting, without taking any of it.
- Front-end delivery with no stylesheet of its own: stable class names, an overridable template,
and
{{ craft.yo.init() }}. - Adoption of Craft's own control panel notices, server-side and in the browser, so every plugin already installed gets Yo without a line of change.
- Dedupe keys, time to live, a per-person cap, and expiry swept with Craft's garbage collection.
- Console commands:
yo/say,yo/channels,yo/types,yo/purge. - Template hooks
yo.panel.header,yo.panel.footerandyo.message.meta.