Nodes without an end time are assigned the "multi-day" CSS class in the calendar month view

Hmm, I don't see this in month view, but instead in day and week views.
I posted a patch to #1269470: All events are shown twice because I had duplicate results, I think the other item was always multiday because of the incorrect date calculations. You can try that patch if it helps.

But as I said, I experience this issue in week and day views.

Have you tried in Views to change the time grouping setting which both the day and the week display offer? Changing that to "hour" might change the events from multi-day to single ones.

Is there any other method than change settings for this one ?
I got the css class turn into multi-day also.

subscribing -- same issue

subscribing -- same issue

My temp fix was to use some jQuery to remove the 'multi-day' class from the td.

I have a node with an end date and I have this issue. Any event on the last day of the month will show as multiday on the first day of the next month.

I have the same problem on both month and week displays.

It's been four months since this issue was opened. Has anyone come up with a workaround?

I've tried to get around it by making the single day and multi-day events look the same via css, but this is rather complicated and one doesn't want to mess up the display of true multi-day events.

I'm bumping the priority.

Setting Mutlti-day style (in the Month Options) as
"Display multi-day item as a single column"
is an easy workaround.

Thank you, @Morn. What you suggest in #10 helps somewhat, in that the text is not truncated, but it makes the true multi-day events appear awkward: they cannot be highlighted by styling, and since they repeat each day, they could become staggered, which would look very sloppy. What is needed is a means of preventing the assignment of the multi-day class to items that are not multi-day.

I experienced this same issue and tracked it to the following line of code.

In calendar_build_week_day function in the calendar_plugin_style.inc file:
change $all_day = $item->calendar_start_date == $item->calendar_end_date;
to $all_day = $item->calendar_all_day;

I don't know if this causes any side-effects, but it seems to fix the problem for me. I hope this helps...I would have submitted a patch for review, but I'm not very familiar with git.

(I originally reported this potential fix in #1264596: Week view shows event in All Day instead of from hour - till hour which I believe was a separate but similar issue.)

Thank you, @bennettee. I'm not using the Week display, but I'll try to see if I can track down similar code that could be affecting the Month display.

@pbfleetwood: IIRC, changing that line fixes all of the displays. It definitely fixes the Month display, though, as that is the only display I am using. Good luck!

Thanks, @bennettee, the code change in #12 works like a charm. I wish that I new a way to override this code without having to directly edit the file in the module; I finally read how to do that with theme_* functions, but that doesn't apply here. Anyway, your fix seems to work very well.

I've made the change to no effect in any view; the td class is still multi-day. Using latest dev releases of Date, Calendar; cleared cache; here's the code for a double-check; anyone see the error?

foreach ($hour as $key => $item) {

// CS Carole replaced this original line with the next one line per http://drupal.org/node/1264520
// $all_day = $item->calendar_start_date == $item->calendar_end_date;
//
$all_day = $item->calendar_all_day;

Thanks Morn your solution worked for me :D

Confirmed the problem and the fix. Thanks!

http://drupalcode.org/project/calendar.git/commit/33abfbb

I applied the patch and still have the issue in Week & Month views. Cleared cache.

This already fixed in dev, there is no patch to apply. You need to use the latest dev of Date and Calendar.

I can reproduce using 7.x-3.x-dev
Seems like there are 2 issues :
An "all day" event is considered as a multi-day.
The multi-day class breaks display (what was the subject of this issue but wasn't fixed).

in calendar_plugin_style.inc, the following needs explanation (and fixes too):
if ($wday == 0 || $start_ydate == $cur_ydate || ($this->date_info->granularity == 'month' && $day_no == 1) || ($all_day && !$is_multi_day))

I've an "all day" event which is not a multi-day, thus :
$all_day = TRUE; $is_multi_day = FALSE
but the above conditional passes, thus $multiday_buckets is filled
thus $multiday_buckets[$wday][$index]['filled'] in calendar_build_month()
thus the display bug.

But even changing this strange condition, $start_ydate == $cur_ydate is TRUE too.
Fixing the CSS would probably be needed too, but there's definitely a bug here which needs to get fixed.

Tested with #16 in newest 7.x-3.x-dev, the issue still occurs with a view built with default template which doesn't have an end date. I've made a patch to fix it. The patch also fixes two issues in other tickets which cause all the events in the 7th day of a week not showing at all (depending on whether Monday or Sunday is set as the first day of a week, this could be Saturday or Sunday), as well as an issue that only the first event is shown for every day if the events are not grouped in the week view. Please check the other two tickets here:
http://drupal.org/node/1779154
http://drupal.org/node/1779142

sorry, please try the latest one

does not solve the bug in my above case
[ please note that your patch is not git-formatted ]

This is still a problem. I worked around it with "Display multi-day item as a multiple column row"

I'm seeing this as well. Events marked as "All day" are treated like Multi-day events, and are adding an empty

Bumping this again - seems like we're still having this issue. My "all day" events are getting the "multi-day" class.

It was still an issue for me, so I wrote a small patch. Hope it will help.

Found a small issue in my patch. When there was no events on week view, you got an error. Fixed in new patch.

#28 solved the problem for me.

Can you remove the changes in the patch that are unrelated to the fix? Sorry I know this is a really late review, but the whitespace fixes cause conflicts with other patches in the queue potentially and make it hard to review the actual fix.

I'm experiencing this with version 7.x-3.6. The above code doesn't seem applicable anymore. Any suggestions?

Some history on how I got here... I updated the Date module from 7.x-2.10 to 7.x-2.11 then back to 7.x-2.10. Most searches around the Date module point back to the Calendar module.

Thank you in advance for any insight.

Drupal 7 reached its end of life in January 2025, and Calendar no longer has an active D7 release. Development and support for D7 are not planned going forward, so we’re marking older D7 issues as outdated to help keep the queue focused on current versions.

If this issue is still relevant for Drupal 10+ or a new release line, please open a follow-up issue or merge request with proposed changes. Contributions are always welcome! 💙