- Issue created by @jmaerckaert
After upgrading to Drupal 11 and Bootstrap 5, the FullCalendar View module (v5.2.4) suffers from a caching regression: the calendar renders correctly immediately after clearing the cache (e.g. via drush cr
), but disappears entirely on subsequent page reloads. This is caused by improper caching of the JavaScript settings (drupalSettings.fullCalendarView
) and attached libraries, which prevents the calendar initialization data from being re-injected on reload.
drush cr
), then navigate to the calendar page – the calendar appears as expected.I’ve prepared a patch that:
#cache
properties) to the render array to prevent dynamic data from being stale or cached improperly.composer.json
to require PHP ≥ 8.3 and declare Drupal 11 compatibility.There are no visible changes to the calendar’s UI. All existing markup and FullCalendar options remain untouched. Bootstrap 5 styling continues to apply as before.
No external module APIs have been altered. Internally, the patch adjusts the preRender()
signature in FullcalendarDisplay.php
and attaches drupalSettings.fullCalendarView
via #attached
on each render. Cache contexts/tags are now declared to ensure proper cache invalidation.
This patch does not introduce any schema or data model changes. All existing configuration entities, field storage, and data tables remain the same.
Needs work
6.0
Code