Re-add full ics export

Feature
1

Hi,

It would be nice to have the behavior that was removed in #231.

Specifically, being able to point an ical client towards events.ics or equivalent to get all events on the site.

Additionally, the DESCRIPTION, URL & ORGANIZER fields are missing from the download-calendar.js replacement. The first two are more important to me.

It would be even nicer to pull in #169 to add “per-topic” event exports, but that’s extra

10 Likes
2

I also would be very happy if I could subscribe to events from my calendar.

Mirroring /upcoming-events I’d love to see a /upcoming-events.ics.

But yeah, having a way to get it for a single category (or even a single tag?) would probably be a great addition too.

Maybe /upcoming-events.ics?category=12 to filter by category id?

2 Likes
3

+1 on full ics feed and filtered by topic.

I know this is hard because of privacy. The usual path is that a random hash feed representing a per user feed is generated.

1 Like
4

umm what … it’s public URL at least with whatever calendar we use …

5

I just want to add my support for this feature as well. I have already voted on this topic.

Bringing back a full-site or per-user ICS export would be extremely valuable for our community’s workflow. Is there any update on reconsidering what was removed in PR #231?

If there are privacy or implementation concerns, perhaps a private, per-user ICS feed could be considered as a solution.

Thanks for considering this!

6

I don’t think there are any privacy concerns, cause the .json endpoint is already there anyway, this is just a different type of formatting.

@cvx / @j.jaffeux thoughts on bringing back .ics to the event index route (removed in: DEV: Remove old ics code by CvX · Pull Request #231 · discourse/discourse-calendar · GitHub) ? Seems like an easy win to me.

We already do:

DiscoursePostEvent::EventFinder.search(current_user, filtered_events_params)

And can have a MAX_RESULTS (order by most recent) to ensure this and the .json don’t get too big.

1 Like