Recurring events in Upcoming Events calendar fail to handle daylight saving change

tshenry · August 28, 2025, 9:39am

It looks like when a recurring event crosses over from one daylight saving state to the other, the time of the event changes by an hour in the Upcoming Events calendar. This will happen even when the event and the user viewing the Upcoming Events calendar have matching timezones.

An easy way to reproduce this is to create an event topic with the following markdown (you may need to change the timezone value in the markdown to your own, or set your user’s timezone to America/Los_Angeles for the sake a reproducing the issue).

[event start="2024-11-01 10:00" status="public" name="Example" url="https://discourse.org" timezone="America/Los_Angeles" recurrence="every_week" minimal="true" end="2024-11-01 11:00"]
[/event]

Once you have created the event, go to /upcoming-events/week/2025/10/27 on your instance. The event will show at the correct time. If you move forward a week (the week daylight saving time ends), it shows the event as an hour earlier.

j.jaffeux · August 28, 2025, 12:55pm

This should have been fixed as part of a bigger fix:

github.com/discourse/discourse

FIX: removes support for include_expired param (#34582)

committed 12:37PM - 28 Aug 25 UTC

jjaffeux

+662 -252

This commit removes the `include_expired` param and its associated site setting …`include_expired_events_on_calendar`. Since recent changes this performance optimisation doesn’t make sense anymore as we only load the events needed for a specific before/after range. The rules are the following: Non recurring events: - They have to have a start date between before/after range Recurring events: - they don't have event_dates, so we don't rely on it for them - what's important for recurring_event, is the recurring_until property and the original starts at - we want to return recurring events when their start date is is after the after param and the before param is before the recurring_until - if recurring_until is NULL we just look at the start date It's done this way as the serializer only sends the rrule to the front, and this is the frontend which will compute the recurring events, but if you want to have all the events of august, and your recurring event is starting in june, you need to also fetch this june event. This commit ensures we can now deal properly with nil dates as it makes no sense to have dates for an expired recurring event.

I tested locally, but let me know if it doesnt work for you.

tshenry · August 29, 2025, 1:21am

I can confirm that this fixes the issue Thanks Joffrey!

Topic		Replies	Views
Recurring events not displaying in the calendar Support calendar-and-event	2	71	January 8, 2025
Upgraded. pre-existing calendar events shifted from local time to UTC Bug calendar-and-event	11	99	January 9, 2025
Recurring not recurring for option other than weekly Bug calendar-and-event	5	752	October 27, 2023
Recurring Events only display current one? Support calendar-and-event	10	901	January 18, 2024
Calendar Plugin all-day events end too soon & render incorrectly Bug	5	557	January 29, 2020

Recurring events in Upcoming Events calendar fail to handle daylight saving change

Related topics