Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
The current date is one day ahead, does not match sitewide timezone when set to that or user timezone either. I have both set the same.
Comment | File | Size | Author |
---|---|---|---|
#7 | time_fix2.patch | 409 bytes | Steve Dondley |
Comments
Comment #1
killes@www.drop.org CreditAttribution: killes@www.drop.org commentedwhich tz are you in, in which tz is your server?
Comment #2
g76 CreditAttribution: g76 commentedThank you for your response, I really appreciate the help.
Timezone: Eastern Standard Time(US): currently it is Friday March 30th, 11:39 am
-Yesterday, March 29th, the calendar read March 30th. It continued to do so even after a fresh install of the latest event module 5.x-2.x, originally I was running 5.x-1.x with the same issue.
-Today the event date reads Friday March 30th, which is correct. I hope it changes tommorrow reflecting the correct date. I will be out of town until Sunday, but will re-check it then and let you know.
Jen
Comment #3
g76 CreditAttribution: g76 commentedWe have a reseller hosting account. Support syas the server is running on Central Daylight Time. Is this an issue?
Comment #4
njbagger CreditAttribution: njbagger commentedI have the exact same problem! Is there a fix to this?
Timezone is Central European standard time (GMT+1).
-Niels
Comment #5
killes@www.drop.org CreditAttribution: killes@www.drop.org commentedI'd like to debug this, can you look into the event table and post the dates that are contained in there?
Comment #6
sdsheridanI'm having this problem too... my event calendar has the 1st of December highlighted now, which isn't 'til tomorrow. But this morning it was the 30th of November...
Comment #7
Steve Dondley CreditAttribution: Steve Dondley commentedHeh, I noticed my date was saying December 1 on Nov 30, too! So, here's a patch.
Comment #8
Steve Dondley CreditAttribution: Steve Dondley commentedComment #9
killes@www.drop.org CreditAttribution: killes@www.drop.org commentedThis appears to be for the 5.1 branch?
Comment #10
Steve Dondley CreditAttribution: Steve Dondley commentedNo, I'm pretty confident it's the latest branch. There may be some line offsets because I had made a hack to the file.
Comment #11
EmpireNM CreditAttribution: EmpireNM commentedThis patch works to fix the date issue, but the current date no longer gets a class of "today". It does get classed as "selected". I'm not sure what that is for. So I used that class to style the current date the calendar instead.
Comment #12
GoofyX CreditAttribution: GoofyX commentedSubscribing...
Comment #13
850 CreditAttribution: 850 commentedI have the same issue also. I tried the patch and changed the class as dlivingstone said which worked in the block, but on the full calendar page it still had a day later highlighted.
Comment #14
japerryEvent for Drupal 8 is unrelated to older versions. If an issue similar to this one exists, please open a new issue with the 8.x branch.