Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
I have an all day event (shared calendar date field across multiple content types: can have end dates, be flagged as all day and recurring) on Monday, 1 Sep 2014 which does not display. If I change the date for the event to all day Tuesday, 2 Sep 2014 it displays fine. If I change the date from all day to start at 07:00 it also displays on Monday, 1 Sep 2014. This infers that the display of the date is affected by the all day flag only on the first day of the month - possibly because the first day in this case is a Monday in the first column???
Comments
Comment #1
JayDarnellI am also having this issue. It happens regardless of whether or not the event is repeating or what month I use.
Comment #2
jazztini CreditAttribution: jazztini commentedSame here. Anything on the first day of the month, all day or otherwise, doesn't show on the month view. It shows on the week or day view just fine.
UPDATE: setting timezone handling to "No time zone conversion" in my Field Settings for the date field causes the event to appear. I'm using a field type of Date (ISO format).
Comment #3
foagth CreditAttribution: foagth commentedI had the same problem with a custom content type of mine.
Date is stored in Unix timestamp format and all my nodes on first day of any month didn't display.
I used hook_views_query_alter to fix this:
'your_datefield' should be replaced with your date field :)
use dpm to confirm the query fields changed.
Moreover, I had to change the Link format in the pager settings to clean urls in order to have the same result when clicking the next months
Comment #4
doppel CreditAttribution: doppel commentedI have the same problem.
tried the code above and got error.
Comment #5
doppel CreditAttribution: doppel commentedThis code works for me. =)
Comment #6
Kasey_MK CreditAttribution: Kasey_MK commentedNeither of these solutions worked for me (I did try changing your_module_query_alter to your_module_views_query_alter in #5).
Comment #7
Kasey_MK CreditAttribution: Kasey_MK commentedAfter lots of experimentation, I discovered that if I un-checked "all day" and entered 11:59pm as the end time, and changed the date's timezone to match the site's timezone, the event would show correctly as an all-day event on the first of the month (and this same adjustment did not break events that were already showing as all-day events on other days of the month).
I wrote a hook_node_presave function to rewrite event dates (where the start datetime and end datetime match each other) as follows: start times to 00:00:00, end times to 23:59:59, and timezone and offsets to match the site's. Multi-day all-day events already appear as expected, so I do not alter those.
I did not have to change the granularity of my date field (minute), though I did change the increment (to 1 minute from 15 minutes). The latter change didn't affect the value stored in the database, but it was confusing to open the node and see 12:00am on the following day for the event end time (the closest 15-minute increment) instead of 11:59pm on the event's last day.
Our site does not allow users to set their own timezone, so I haven't tested for that possibility. This solution allows us to keep our site's timezone (instead of setting it to UTC), as well as the date's timezone (so we can display events across multiple regions).
Comment #8
Michael_Lessard_micles.biz CreditAttribution: Michael_Lessard_micles.biz commentedFrom what I can tell on my set-up :
a) Overall site settings : local timezone (GTM-5) ;
b) Date Field (in my event node type) set to not do any timezone conversions ;
c) Monthly Calendar Views is evidently set to GMT-0, so some events at the beginning and end of the month can get flushed over to the wrong month.
If I am correct. this means it is something that needs to be fixed in the Calendar View or module as such.EDIT: Turns out I needed to set my Date Fields to my same site timezone initially.
So I just did: set event Date Field to "same as site" and it fixed it.
( but maybe the installation Read Me text or documentation should explain about the timezone misconfigurations.)
Comment #9
merrizervas CreditAttribution: merrizervas commentedComment #10
izmeez CreditAttribution: izmeez commentedComment #11
apadernoComment #12
Neslee Canil Pinto