# Discourse Agenda bijgewerkt om fullcalendar 6 te gebruiken

**URL:** https://meta.discourse.org/t/discourse-calendar-updated-to-use-fullcalendar-6/380311
**Category:** Announcements
**Tags:** events
**Created:** [26 augustus 2025 om 09:24 UTC](https://meta.discourse.org/t/discourse-calendar-updated-to-use-fullcalendar-6/380311 "2025-08-26T09:24:45Z")
**Posts on this page:** 20
**Page:** 1

<div class="post-metadata">

### Author: ![j.jaffeux](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/j.jaffeux/32/60297_2.png) [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)
#### Post date: [26 augustus 2025 om 09:24 UTC](https://meta.discourse.org/t/discourse-calendar-updated-to-use-fullcalendar-6/380311/1 "2025-08-26T09:24:45Z")

</div>

Discourse calendar received [a significant update today](https://github.com/discourse/discourse/commit/361029ad4d96dc6cb2fa1d246a0083fc9313e7b0) 🚀. The core of the update is migrating from fullcalendar 4 to [fullcalendar 6](https://fullcalendar.io/) which will bring us an updated UI:

 ![Screenshot 2025-08-26 at 11.23.35](https://global.discourse-cdn.com/meta/original/4X/1/1/3/113d830acba5ed859981324ebf233c9b454c751f.png)

We also used this opportunity to make the following changes:

- Clean URLs for upcoming events page, eg: `/upcoming-events/day/2025/8/2`

- Post event preview on click over an event

 ![Screenshot 2025-08-26 at 11.22.57](https://global.discourse-cdn.com/meta/original/4X/c/3/f/c3fba9da26d28cd33498748fdc75e8f2dde723ae.png)

- Performance has been vastly improved and having a large number of events should now be possible.

- We now rely on the css variables provided by fullcalendar which should make the calendar work with your theme out of the box.

---

<div class="post-metadata">

### Author: ![gilles](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gilles/32/549022_2.png) [@gilles](https://meta.discourse.org/u/gilles)
#### Post date: [26 augustus 2025 om 13:37 UTC](https://meta.discourse.org/t/discourse-calendar-updated-to-use-fullcalendar-6/380311/2 "2025-08-26T13:37:29Z")

</div>

Bravo, great job, thank you very much 😍

---

<div class="post-metadata">

### Author: ![gilles](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gilles/32/549022_2.png) [@gilles](https://meta.discourse.org/u/gilles)
#### Post date: [26 augustus 2025 om 13:51 UTC](https://meta.discourse.org/t/discourse-calendar-updated-to-use-fullcalendar-6/380311/3 "2025-08-26T13:51:10Z")

</div>

Klein vraagje, kunnen we (year) als standaard instellen voor het mobiele gedeelte?  
Anders is het weer top!!

---

<div class="post-metadata">

### Author: ![opcourdis](https://avatars.discourse-cdn.com/v4/letter/o/45deac/32.png) [@opcourdis](https://meta.discourse.org/u/opcourdis)
#### Post date: [27 augustus 2025 om 01:27 UTC](https://meta.discourse.org/t/discourse-calendar-updated-to-use-fullcalendar-6/380311/4 "2025-08-27T01:27:12Z")

</div>

> [@j.jaffeux](#):
>
> - Clean URLs for upcoming events page, eg: `/upcoming-events/day/2025/8/2`
> - Post event preview on click over an event

Thank you for the work ! Is both US/EU date format system supported for those url? and what if there are several events on the same day?

---

<div class="post-metadata">

### Author: ![j.jaffeux](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/j.jaffeux/32/60297_2.png) [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)
#### Post date: [27 augustus 2025 om 06:09 UTC](https://meta.discourse.org/t/discourse-calendar-updated-to-use-fullcalendar-6/380311/5 "2025-08-27T06:09:07Z")

</div>

Sorry, we will support only one URL format for now.

That doesn’t prevent you from seeing all the events on this day/month/year. If you want to link to an event directly, link to the event post.

---

<div class="post-metadata">

### Author: ![opcourdis](https://avatars.discourse-cdn.com/v4/letter/o/45deac/32.png) [@opcourdis](https://meta.discourse.org/u/opcourdis)
#### Post date: [27 augustus 2025 om 09:44 UTC](https://meta.discourse.org/t/discourse-calendar-updated-to-use-fullcalendar-6/380311/6 "2025-08-27T09:44:43Z")

</div>

Inderdaad kan de directe link naar het evenement worden gedeeld en het verstrekken van meerdere URL-formaten is geen gemakkelijke taak. We zijn al dankbaar dat u ons deze update voor fullcalendar 6 met nieuwe functies biedt!

---

<div class="post-metadata">

### Author: ![stephen34](https://avatars.discourse-cdn.com/v4/letter/s/ba9def/32.png) [@stephen34](https://meta.discourse.org/u/stephen34)
#### Post date: [28 augustus 2025 om 00:36 UTC](https://meta.discourse.org/t/discourse-calendar-updated-to-use-fullcalendar-6/380311/7 "2025-08-28T00:36:27Z")

</div>

Sinds de upgrade zie ik instanties van een verschil van 1 uur tussen de posttijd van het onderwerp (correct) en de kalendertijdweergave (een uur eerder) op _sommige_ gebeurtenissen, maar niet alle.

Dit wordt ofwel opgelost nadat onze lokale tijdzone naar zomertijd overschakelt, ofwel worden sommige andere gebeurtenissen (omgekeerd) beïnvloed nadat de zomertijd begint. Niet alle gebeurtenissen worden echter beïnvloed. Is dit een bekend probleem? Is er een oplossing in de pijplijn?

#Bug

---

<div class="post-metadata">

### Author: ![nathank](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/nathank/32/290039_2.png) [@nathank](https://meta.discourse.org/u/nathank)
#### Post date: [28 augustus 2025 om 00:52 UTC](https://meta.discourse.org/t/discourse-calendar-updated-to-use-fullcalendar-6/380311/8 "2025-08-28T00:52:18Z")

</div>

This is brilliant! It really lifts the calendar to the next level.

I notice that the text of the event titles doesn’t wrap in the (default) Month view. Is this intentional?

### Desktop Calendar

 ![image](https://global.discourse-cdn.com/meta/original/4X/f/b/4/fb457ec66878719b7c728aaa19d69b5a874a7e81.png)

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.

 ![Mobile Calendar](https://global.discourse-cdn.com/meta/original/4X/9/4/6/946b34c7d03114e5290928cd9ec700b5c76da06f.png)

### An agenda view?

Lastly, it would be super helpful to have an agenda view, which is a common way of representing events. Is this at all possible via the calendar?

I know that it is doable using the [Right Sidebar Blocks](https://meta.discourse.org/t/right-sidebar-blocks/231067), but that is in a different context.

---

<div class="post-metadata">

### Author: ![j.jaffeux](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/j.jaffeux/32/60297_2.png) [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)
#### Post date: [28 augustus 2025 om 05:52 UTC](https://meta.discourse.org/t/discourse-calendar-updated-to-use-fullcalendar-6/380311/9 "2025-08-28T05:52:52Z")

</div>

Ja, ik zal dit vandaag repareren, ik wacht op een definitieve repro, bedankt.

---

<div class="post-metadata">

### Author: ![j.jaffeux](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/j.jaffeux/32/60297_2.png) [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)
#### Post date: [28 augustus 2025 om 12:56 UTC](https://meta.discourse.org/t/discourse-calendar-updated-to-use-fullcalendar-6/380311/10 "2025-08-28T12:56:07Z")

</div>

Should have been fixed by: [FIX: removes support for include\_expired param (#34582) · discourse/discourse@249ae00 · GitHub](https://github.com/discourse/discourse/commit/249ae0009ac208ecf5c49dd29db8ded4d244fc75)

---

<div class="post-metadata">

### Author: ![gilles](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gilles/32/549022_2.png) [@gilles](https://meta.discourse.org/u/gilles)
#### Post date: [28 augustus 2025 om 13:34 UTC](https://meta.discourse.org/t/discourse-calendar-updated-to-use-fullcalendar-6/380311/11 "2025-08-28T13:34:47Z")

</div>

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! 😇

---

<div class="post-metadata">

### Author: ![j.jaffeux](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/j.jaffeux/32/60297_2.png) [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)
#### Post date: [28 augustus 2025 om 14:20 UTC](https://meta.discourse.org/t/discourse-calendar-updated-to-use-fullcalendar-6/380311/12 "2025-08-28T14:20:34Z")

</div>

Ik denk dat het algemeen verwacht wordt dat het vandaag opengaat. Als je je gebruikers aan een specifieke dag wilt koppelen, kun je nu de gewenste link maken: /upcoming-events/day/2025/9/2

---

<div class="post-metadata">

### Author: ![hellekin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/hellekin/32/51636_2.png) [@hellekin](https://meta.discourse.org/u/hellekin)
#### Post date: [28 augustus 2025 om 14:44 UTC](https://meta.discourse.org/t/discourse-calendar-updated-to-use-fullcalendar-6/380311/13 "2025-08-28T14:44:06Z")

</div>

Thank you!

> [@j.jaffeux](#):
>
> Clean URLs for upcoming events page, eg: `/upcoming-events/day/2025/8/2`

Would following ISO date format be possible? As in YYYY/MM/DD (two digits for months and days)?

---

<div class="post-metadata">

### Author: ![j.jaffeux](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/j.jaffeux/32/60297_2.png) [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)
#### Post date: [28 augustus 2025 om 14:47 UTC](https://meta.discourse.org/t/discourse-calendar-updated-to-use-fullcalendar-6/380311/14 "2025-08-28T14:47:29Z")

</div>

Im mostly following what google is doing here:

![Screenshot 2025-08-28 at 15.47.18](https://global.discourse-cdn.com/meta/original/4X/7/f/b/7fbcff6c5eac72de1fb88697332e6d3b253dafd0.png)

---

<div class="post-metadata">

### Author: ![hellekin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/hellekin/32/51636_2.png) [@hellekin](https://meta.discourse.org/u/hellekin)
#### Post date: [28 augustus 2025 om 14:48 UTC](https://meta.discourse.org/t/discourse-calendar-updated-to-use-fullcalendar-6/380311/15 "2025-08-28T14:48:20Z")

</div>

Ah, why would they follow standards when they can break it and create more work for others. 🤦

---

<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: [29 augustus 2025 om 01:55 UTC](https://meta.discourse.org/t/discourse-calendar-updated-to-use-fullcalendar-6/380311/16 "2025-08-29T01:55:40Z")

</div>

Moeite om te begrijpen waarom `/day/2025/09/01` zoveel beter is dan `/day/2025/9/1`

Ik zou stellen dat het slechter is om de nullen toe te voegen, omdat het meer ruimte inneemt in de balk.

---

<div class="post-metadata">

### Author: ![nathank](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/nathank/32/290039_2.png) [@nathank](https://meta.discourse.org/u/nathank)
#### Post date: [29 augustus 2025 om 02:17 UTC](https://meta.discourse.org/t/discourse-calendar-updated-to-use-fullcalendar-6/380311/17 "2025-08-29T02:17:46Z")

</div>

Het is niet _beter_. Gewoon meer gestandaardiseerd en consistent met hoe _datums_ in andere delen van Discourse worden gecodeerd.

Daarentegen is de manier waarop het momenteel is geïmplementeerd consistent met Discourse URL’s (die open-eindige nummering moeten hebben).

Dit is dus een filosofische beslissing. Interne consistentie met URL’s of interne/externe consistentie met datums. Er zijn voor- en nadelen aan beide. Ik geef de voorkeur aan de huidige implementatie.

---

<div class="post-metadata">

### Author: ![Jagster](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jagster/32/192154_2.png) [@Jagster](https://meta.discourse.org/u/Jagster)
#### Post date: [29 augustus 2025 om 04:13 UTC](https://meta.discourse.org/t/discourse-calendar-updated-to-use-fullcalendar-6/380311/18 "2025-08-29T04:13:26Z")

</div>

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.

---

<div class="post-metadata">

### Author: ![hellekin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/hellekin/32/51636_2.png) [@hellekin](https://meta.discourse.org/u/hellekin)
#### Post date: [30 augustus 2025 om 09:15 UTC](https://meta.discourse.org/t/discourse-calendar-updated-to-use-fullcalendar-6/380311/19 "2025-08-30T09:15:19Z")

</div>

Ha! Sorry, ik wilde niet over details discussiëren. Puur getallen worden numeriek gesorteerd, leidende nullen zorgen ervoor dat maanden in de juiste volgorde verschijnen.

---

<div class="post-metadata">

### Author: ![stephen34](https://avatars.discourse-cdn.com/v4/letter/s/ba9def/32.png) [@stephen34](https://meta.discourse.org/u/stephen34)
#### Post date: [1 september 2025 om 03:01 UTC](https://meta.discourse.org/t/discourse-calendar-updated-to-use-fullcalendar-6/380311/20 "2025-09-01T03:01:14Z")

</div>

Ik zie nog steeds afwijkend gedrag van terugkerende gebeurtenissen voor en na lokale tijdswijzigingen naar zomertijd. We hebben een gehost abonnement, dus is het slechts een kwestie van wachten tot de oplossing is doorgevoerd?

[Volgende pagina](https://meta.discourse.org/t/discourse-calendar-updated-to-use-fullcalendar-6/380311.md?page=2)
