# Undefined ICS file name

**URL:** https://meta.discourse.org/t/undefined-ics-file-name/387696
**Category:** Bug
**Tags:** events
**Created:** [November 5, 2025, 5:55pm UTC](https://meta.discourse.org/t/undefined-ics-file-name/387696 "2025-11-05T17:55:36Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [November 6, 2025, 1:24am UTC](https://meta.discourse.org/t/undefined-ics-file-name/387696/3 "2025-11-06T01:24:17Z")

</div>

This is a tricky one Dax which is a side effect of our pipeline.

We generate the bbcode for the dates here:

> <https://github.com/discourse/discourse/blob/d440592f88c425347d9a1115d6357ddcc7ec3ea8/plugins/discourse-calendar/assets/javascripts/discourse/components/discourse-post-event/dates.gjs#L76-L97>

And cook it here:

> <https://github.com/discourse/discourse/blob/d440592f88c425347d9a1115d6357ddcc7ec3ea8/plugins/discourse-calendar/assets/javascripts/discourse/components/discourse-post-event/dates.gjs#L141-L141>

So in the context of the cooked chunk of html the “download ics” is not aware of the actual post it is on (or event)

We also have a **different** pipeline for ics generation at:

> <https://github.com/discourse/discourse/blob/d440592f88c425347d9a1115d6357ddcc7ec3ea8/frontend/discourse/app/lib/download-calendar.js#L14-L14>

So we need to decide from an engineering perspective if:

1. We teach the “date cooking” how to re-route ics generation to Discourse Calendar.

OR

1. We provide enough context to Discourse Local Dates, so it can independently generate the ics and keep the code fractured.

I am not sure what the correct thing is to do here, but I have prioritized it so the team can triage and sort it out.

---

_[View the full topic](https://meta.discourse.org/t/undefined-ics-file-name/387696)._