{"id":"6a2d42c892933859b92c3a80","title":"2026 06 13 Build 692","path":"how-to/committee/release-notes/2026-06-13-build-692","contentMarkdown":"# 13-Jun-2026 — booking emails: per-event wording, global defaults and inline send status [ref #273](https://github.com/nbarrett/ngx-ramblers/issues/273)\n\n## [build 692](https://github.com/nbarrett/ngx-ramblers/actions/runs/27465634826) — [commit 38e80f6](https://github.com/nbarrett/ngx-ramblers/commit/38e80f62f2b3b4944aeda006a3ca9679d6194970)\n\n_____\n\n## In plain English\n\nThe booking emails your site sends (confirmation, cancellation, waiting list, place restored and reminder) can be tailored for a single event, and this release makes that flow clearer and quicker to use.\n\n- **Each event can have its own wording.** Choose **Admin** then **Bookings**, open the **Per-Event Detail** tab and pick an event. Under **Per-event email overrides** each of the five booking emails offers **Standard wording** or **Customise**.\n- **Standard wording now means your group's own default.** It reads from the global Booking Notification template (set under Mail Settings > Email Configurations > Booking Notification), so when you reword the global template, every event you have not customised picks up the change automatically.\n- **Clearing a customisation now sticks.** Removing all of an event's overrides restores it to the standard wording and the change no longer reappears when you reload the page.\n\n![](https://ngx-ramblers.org.uk/api/aws/s3/site-content/d3a2ded6-415e-42d3-8208-428585bcd35d.png)\n\n*Per-event email overrides: with Standard wording selected, the editor shows the group's global booking wording, ready to Customise for this event*\n\n## Sending confirmation emails\n\nFrom the same per-event view you can send the confirmation emails to everyone booked on the event. The **Send confirmation emails now** button now shows its progress and result beside the button: it is disabled while sending, shows a spinner, and reports the outcome (for example \"3 sent, 2 already sent\") when it finishes, instead of a separate alert at the top of the page.\n\n![](https://ngx-ramblers.org.uk/api/aws/s3/site-content/3bc0e802-1c9f-4635-a232-df264e6e62f3.png)\n\n*The Send confirmation emails now button, where the sending progress and result now appear inline*\n\nFor the full step-by-step guide to booking email wording, see [Customising Email Wording](https://ngx-ramblers.org.uk/how-to/committee/email-articles/customising-email-wording).\n\n## The technical detail\n\n### Booking email fixes and inline send status\n\n- **Site-level template as default**: The \"Standard wording\" option in the\nper-event booking editor now reads from the site-level Booking Notification\nconfig (set under Mail Settings > Email Configurations), rather than using\nthe hardcoded constant. This means changes to the global template are\nreflected immediately in the per-event editor.\n\n- **Empty override save fix**: Previously, clearing all per-event overrides\nsent an empty object `{}` to the server, which did not trigger a database\nunset. The field now sends `null` when no overrides remain, so the old\ndata is properly removed and does not reappear on page reload.\n\n- **Inline send status**: The \"Sending: Dispatching confirmation emails...\"\nmessage now appears inline next to the Send button instead of in the\ntop-of-page alert area. The button is disabled while dispatching, shows a\nspinning icon, and displays the dispatch result (e.g. \"Event: 3 sent, 2\nalready sent\") next to the button when complete.","contentHtml":"<h1>13-Jun-2026 — booking emails: per-event wording, global defaults and inline send status <a href=\"https://github.com/nbarrett/ngx-ramblers/issues/273\">ref #273</a></h1>\n<h2><a href=\"https://github.com/nbarrett/ngx-ramblers/actions/runs/27465634826\">build 692</a> — <a href=\"https://github.com/nbarrett/ngx-ramblers/commit/38e80f62f2b3b4944aeda006a3ca9679d6194970\">commit 38e80f6</a></h2>\n<hr>\n<h2>In plain English</h2>\n<p>The booking emails your site sends (confirmation, cancellation, waiting list, place restored and reminder) can be tailored for a single event, and this release makes that flow clearer and quicker to use.</p>\n<ul>\n<li><strong>Each event can have its own wording.</strong> Choose <strong>Admin</strong> then <strong>Bookings</strong>, open the <strong>Per-Event Detail</strong> tab and pick an event. Under <strong>Per-event email overrides</strong> each of the five booking emails offers <strong>Standard wording</strong> or <strong>Customise</strong>.</li>\n<li><strong>Standard wording now means your group&#39;s own default.</strong> It reads from the global Booking Notification template (set under Mail Settings &gt; Email Configurations &gt; Booking Notification), so when you reword the global template, every event you have not customised picks up the change automatically.</li>\n<li><strong>Clearing a customisation now sticks.</strong> Removing all of an event&#39;s overrides restores it to the standard wording and the change no longer reappears when you reload the page.</li>\n</ul>\n<p><img src=\"https://ngx-ramblers.org.uk/api/aws/s3/site-content/d3a2ded6-415e-42d3-8208-428585bcd35d.png\" alt=\"\"></p>\n<p><em>Per-event email overrides: with Standard wording selected, the editor shows the group&#39;s global booking wording, ready to Customise for this event</em></p>\n<h2>Sending confirmation emails</h2>\n<p>From the same per-event view you can send the confirmation emails to everyone booked on the event. The <strong>Send confirmation emails now</strong> button now shows its progress and result beside the button: it is disabled while sending, shows a spinner, and reports the outcome (for example &quot;3 sent, 2 already sent&quot;) when it finishes, instead of a separate alert at the top of the page.</p>\n<p><img src=\"https://ngx-ramblers.org.uk/api/aws/s3/site-content/3bc0e802-1c9f-4635-a232-df264e6e62f3.png\" alt=\"\"></p>\n<p><em>The Send confirmation emails now button, where the sending progress and result now appear inline</em></p>\n<p>For the full step-by-step guide to booking email wording, see <a href=\"https://ngx-ramblers.org.uk/how-to/committee/email-articles/customising-email-wording\">Customising Email Wording</a>.</p>\n<h2>The technical detail</h2>\n<h3>Booking email fixes and inline send status</h3>\n<ul>\n<li><p><strong>Site-level template as default</strong>: The &quot;Standard wording&quot; option in the\nper-event booking editor now reads from the site-level Booking Notification\nconfig (set under Mail Settings &gt; Email Configurations), rather than using\nthe hardcoded constant. This means changes to the global template are\nreflected immediately in the per-event editor.</p>\n</li>\n<li><p><strong>Empty override save fix</strong>: Previously, clearing all per-event overrides\nsent an empty object <code>{}</code> to the server, which did not trigger a database\nunset. The field now sends <code>null</code> when no overrides remain, so the old\ndata is properly removed and does not reappear on page reload.</p>\n</li>\n<li><p><strong>Inline send status</strong>: The &quot;Sending: Dispatching confirmation emails...&quot;\nmessage now appears inline next to the Send button instead of in the\ntop-of-page alert area. The button is disabled while dispatching, shows a\nspinning icon, and displays the dispatch result (e.g. &quot;Event: 3 sent, 2\nalready sent&quot;) next to the button when complete.</p>\n</li>\n</ul>\n"}