Using "Default date source: Date of first view result" causes JS error

Created on 15 June 2023, over 1 year ago
Updated 30 November 2023, about 1 year ago

When choosing the option for Default date source labeled Date of first view result, the full calendar fails to load. In console there is an error:
"Uncaught (in promise) TypeError: e is null". This happens both when viewing the View page and when previewing it in the view settings.

Drupal 9.5.5
Full Calendar 4.4.2
Fullcalendar View 5.1.12

πŸ› Bug report
Status

Postponed: needs info

Version

5.1

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States fallenturtle

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

Comments & Activities

  • Issue created by @fallenturtle
  • πŸ‡¦πŸ‡ΊAustralia mingsong πŸ‡¦πŸ‡Ί

    What is the result if you choose other display format for that view?

    More specifically, what is the date of the first row of the result? If it is not a validated date format or is null. The calendar view won't work.

  • Status changed to Postponed: needs info over 1 year ago
  • πŸ‡¦πŸ‡ΊAustralia mingsong πŸ‡¦πŸ‡Ί
  • πŸ‡ΊπŸ‡ΈUnited States fallenturtle

    It's my oldest event.

  • I also have this issue.
    I am using a single smart date field

    • format Smart date Formatter
    • timepart start and end
    • tisamrt date format : default

    The browser console shows

    Uncaught TypeError: Cannot read properties of null (reading 'getUTCFullYear')
        at B (main.min.js:6:4632)
        at e.startOf (main.min.js:6:62456)
        at d (main.min.js:6:69617)
        at e.buildRangeFromDuration (main.min.js:6:69815)
        at e.buildCurrentRangeInfo (main.min.js:6:68908)
        at e.build (main.min.js:6:68116)
        at main.min.js:6:72011
        at er (main.min.js:6:72235)
        at e.reduce (main.min.js:6:90654)
        at e.dispatch (main.min.js:6:89995)
Production build 0.71.5 2024