The Discourse calendar plugin has received a significant update, migrating from FullCalendar 4 to FullCalendar 6 to improve the UI, performance, and theme compatibility j.jaffeux. Key changes include clean URLs for event pages (e.g., /upcoming-events/day/2025/8/2), event previews on click, and better handling of large event lists j.jaffeux. While the community praised the update, several issues and feature requests were raised:
Date Formats: A discussion ensued regarding the URL format. The developer chose to follow Google’s style with leading zeros (YYYY/MM/DD) for internal consistency with Discourse dates, despite some users preferring the shorter format j.jaffeux, sam, nathank.
Time Zone Bugs: Users reported a 1-hour discrepancy in event times around daylight saving changes stephen34. The developer confirmed this was a known issue and provided a fix j.jaffeux.
UI/Display Issues: Concerns were raised about event titles not wrapping in Month view nathank, Magie. The developer clarified that titles will remain single-line to maximize space, though a user shared a CSS workaround to enable two lines paulswithers. Additionally, the developer confirmed that multi-day events in category calendars will be fixed in the next update j.jaffeux.
Interaction Behavior: Users requested that clicking an event in category calendars show the overlay instead of redirecting to the topic immediately Magie, Tonja. The developer noted this is currently the intended behavior but acknowledged the feedback.
Future Features: Suggestions included defaulting to a list view on mobile gilles, adding an agenda view nathank, and improving recurring event topic generation opcourdis, all of which the team acknowledged as future steps.
Discourse calendar received a significant update today. The core of the update is migrating from fullcalendar 4 to fullcalendar 6 which will bring us an updated UI:
Indeed the direct link to the event can be shared and providing multiple url format is not an easy task. We are already thankful that you are providing us with this update to fullcalendar 6 with new features !
Since the upgrade I’m seeing instances of a 1 hour difference between the topic post time (correct) and the calendar display time (one hour earlier) on some events, but not all.
This either resolves after our local time zone switches to summer time or throws out some other events (in reverse) after daylight saving starts. Not all events are affected however. Is this a known issue? Is there a fix in the pipeline?
It would be nice to see the whole titles in the Month view on desktop (?perhaps on hover), as these are often packed with useful information. Of course, that would mean that the events could get greedy and take up more space.
Mobile Calendar
Also, in mobile it is rare to see more than the time. I guess this doesn’t matter so much as it is easy to tap them to see more.
I have a small suggestion:sweat_smile:
Instead of going to today’s date, wouldn’t it be better to go directly to the date of the next event?
It’s just an idea!
I think it’s generally expected to open today. I you need to link your users to a specific day you can just craft the link you want now: /upcoming-events/day/2025/9/2
It isn’t better. Just more standardised, and consistent with how dates are encoded in other parts of Discourse.
On the converse, the way it is currently implemented is consistent with Discourse URLs (which need to have open-ended numbering).
So, this is a philosophical decision. Internal consistency with URLs or internal/external consistency with dates. There are pros and cons for each. I prefer the current implementation.
If I would start write that date the form would be mm/dd. Because it is a standard practically everywhere — except when connection is from US and they would drop leading zeros and and start words with capital letters . Or from coders who count spaces, because even americans can read and use mm/dd.
So, it is matter of muscle memory and a factoid that most of the word is used to use ISO format and it is hard to remember which software and platform uses which format. That is one of those questions where always someone loses — the question is which group is the biggest.
I’m still seeing errant behaviour of recurring events before and after local time changes to daylight saving time. We are on a hosted plan, so is it just a matter of waiting for the fix to be pushed through?