Full day event appears on two calendar days when scheduled the day before Daylight Savings Time change

Created on 20 August 2024, 3 months ago

Problem/Motivation

I have a full day event (created using the smart_date module) scheduled on March 8, 2025. The fullcalendar_view calendar shows this event spanning March 8-March 9, 2025. If I change the date of the event to any other date (ex, March 9, 2025), it only shows on one day of the calendar, as expected.

The issue is reproducible in other years when a full day event is scheduled the day before the switch to daylight savings time. For example, if I schedule an event on March 7, 2026, the event is shown on two pages of the calendar.

Steps to reproduce

1) Install and enable the smart_date and fullcalendar_view modules.
2) Set your site's default time zone to 'Toronto' (/admin/config/regional/settings). Do not allow users to set their own timezones.
3) Create an 'Event' content type with a smart date range field named 'Date'.
4) Create an 'Event' node named 'Test Event' and set the 'Date' field to 'March 8, 2025'. Select 'All day' for the duration of the event.
5) Create a view using the Full Calendar Display display format and a page display.
6) Add the 'Date' field to the fields in the view.
7) In the Full Calendar Display settings, select the 'Date' field for the Start Date Field and End Date Field.
8) Navigate to the page display of the Events view and click next arrow until the calendar is showing March 2025.

The 'Test Event' shows on both March 8 and 9th. It should only show on March 8th.

🐛 Bug report
Status

Active

Version

5.2

Component

Code

Created by

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @flitt1
  • 🇦🇺Australia mingsong 🇦🇺

    Thanks for reporting this issue.

    I wonder if it is an issue with the Fullcalendar.js. Because this module doesn't provide additional logic to daylight saving, it relies on the Fullcalendar.js to deal with the time change.

    If anyone came across this issue or have any clue to fix this issue, please help.

Production build 0.71.5 2024