Ampersand wird bei synchronisierten Ereignissen nicht richtig angezeigt

zogstrip · 8. April 2026 um 14:12

Danke für den Bericht @nathank Es wird durch

github.com/discourse/discourse

FIX: Prevent HTML-encoding of special characters in ICS feeds (#39152)

main ← fix/ics-ampersand-encoding

opened 02:11PM - 08 Apr 26 UTC

ZogStriP

+45 -3

ERB's `<%= %>` calls `ERB::Util.html_escape` on all non-`html_safe` strings, eve…n in non-HTML templates like `.ics.erb`. This caused ampersands (and potentially other special characters) to be double-encoded as `&` in calendar subscription feeds, which external calendar apps like Google Calendar displayed verbatim. Mark `IcalEncoder.encode` output as `html_safe` since it already performs all necessary ICS encoding (HTML sanitization, entity decoding, RFC 5545 escaping). Also route the URL fields in both ICS templates through `IcalEncoder.encode` for consistency. https://meta.discourse.org/t/400166

behoben.

Thema		Antworten	Aufrufe
Discourse email notification shows HTML entities for ampersand etc Support	5	882	6. Januar 2021
Calendar event seems broken? Bug calendar-and-event , fixed	12	187	27. Juni 2025
The webcal URL is incorrectly passed to the Calendar Name field in Google Calendar Bug calendar-and-event , fixed	7	47	8. April 2026
Ampersands getting over-escaped going from Wordpress to Discourse? WordPress	10	623	2. Mai 2024
Ampersand (&) doesn't 'display' right if from linked post Bug	5	1376	9. Mai 2017

Ampersand wird bei synchronisierten Ereignissen nicht richtig angezeigt

Verwandte Themen