Closed (duplicate)
Project:
Calendar
Version:
8.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
10 Sep 2024 at 06:25 UTC
Updated:
18 Mar 2025 at 14:44 UTC
Jump to comment: Most recent
Comments
Comment #2
avpadernoComment #3
avpadernoComment #4
ttnt commentedSeeing exactly the same, which is too bad as it seems it's the most stable calendar option currently available. Anyone knows why this happens and what could be done about this? This makes it a bit unusable right now.
Edit: or if anyone has found usable alternatives to calendar which can handle multi-month entries, feel free to share. I tried full-calendar but that bricks the view when adding custom fields.
Comment #5
auseidon986 commentedThis issue was reported already years ago :
https://www.drupal.org/project/calendar/issues/3358750
And it 's so sad there is no fix made yet.
Comment #6
auseidon986 commentedComment #7
ttnt commentedWait - that's odd, I only see this in my D10 instance, an older D7 that was the basis for the D10 I now run didn't have this issue at all. So the issue must have been solved once, but now returned?
It works in: core 7.103 calendar 7.x-3.6
It does not work in: core 10.4.1 calendar 8.x-1.0-beta3
Edit: I see now that "years ago" doesn't mean D7, I only switched recently ;). Too bad, if that would have been the case a fix could have been obvious from changes in the codebase. I may give it another go to see where things went wrong between versions but so far I haven't been able to figure it out either... I have a dark brown feeling it has something to do with the end date being in core for D7 but not in D8+. I'm currently using datetime range for this myself as it came with core and I assumed this is how later Drupal versions would integrate end dates permanently, but now I see smart date being recommended for Drupal CMS and I have no clue if this will matter for an eventual workaround.
Comment #8
ttnt commentedFound another issue: full-day reservations on the first day of the month (so for example starting 1/04 00:00) also do not display in Drupal calendar. Probably 1/04 00:00 is seen as 31/03 00:00 and thus doesn't carry over to the next month.
Any help with this is very much appreciated, this module is really the fastest among all Drupal calendar options so I'd prefer to keep using it.
Comment #9
avpaderno