Sería mejor incluir la descripción en las notificaciones por correo electrónico de eventos y temas

zogstrip · 15 Junio, 2026 12:41

Gracias, se solucionará en

github.com/discourse/discourse

FIX: Include full event details in notification emails (#40880)

main ← fix-event-email-details

merged 03:10PM - 02 Jul 26 UTC

ZogStriP

+453 -75

Previously, the notification email for an event post showed almost nothing abou…t the event. The event card is rendered client-side from the `[event]` block's `data-*` attributes, so emails (which run no JavaScript) fell back to a sparse table that omitted the description entirely and mishandled other fields: all-day events showed a bogus "12:00 AM", recurring events gave no hint that they repeat, and scheme-less URLs produced broken relative links. This change extracts the email rendering into a dedicated `DiscoursePostEvent::EmailRenderer` that mirrors the on-site event card as closely as a static rendering allows. The email now includes the description, status (e.g. Expired/Closed), creator, recurrence label, "N going" count and cover image; formats all-day dates without a spurious time/timezone; renders emoji in the event name; cooks markdown in the location; and prepends a scheme to scheme-less URLs. Translations are read from the existing client locale (the `js.*` namespace) so the email and the card never drift, and recurrence/status values are gated by `EventValidator::VALID_RECURRENCES` and the event's own status. Purely interactive parts of the card (RSVP buttons, chat-channel link, more menu) are intentionally omitted. The creator is shown according to the site's name settings (`display_name` gated by `enable_names`) rather than always exposing the real name, which matches the on-site card and the other surfaces these emails reach, such as embedded comments. `PrettyText.format_for_email` does no sanitization of its own, so every field is escaped where it is rendered. Description URLs are linkified by escaping each text segment independently, keeping any markup that follows a URL out of the generated `href`. Finally, rendering is resilient: a failure on a single event is rescued and logged so one malformed event can never abort an entire digest or notification email. **BEFORE / AFTER** <img width="2720" height="1666" alt="before_after" src="https://github.com/user-attachments/assets/fe3aa7ce-7659-42c6-8c84-628516c92fdc" />

Tema		Respuestas	Vistas
"Add To Calendar" - .ics iCal attachments for Events in Discourse notification emails? Feature calendar-and-events	6	229	13 Abril 2026
Event description not translated by AI Translation plugin (discourse-calendar) Feature calendar-and-events , content-localization	0	51	9 Abril 2026
📅 Question: Include event details when saving to calendar UX calendar-and-events , completed	4	194	28 Abril 2026
Email excerpts rather than full posts Feature	23	2875	21 Agosto 2019
Subscription emails should carry more context in message body Feature	5	3341	13 Marzo 2016

Sería mejor incluir la descripción en las notificaciones por correo electrónico de eventos y temas

Temas relacionados