Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By susata on
Problem: My calendar says it is 8 or 9 hours into the future, which means that later in the day the next day gets highlighted as the current date.
Note: I have found discussion about the date being off by some hours in past posts, but I am unable to determine from these posts if a resolution was ever found (I am a Drupal newbie and am a bit lost when talk drifts into php code, patches, etc.). I would immensely appreciate getting directed to the elucidating post that I may have missed, where I can learn either how to correct my calendar functionality or if this is an issue that has not yet been addressed--but is known.
More background:
Today I installed Drupal 5.5, Date 1.8, Calendar 1.7, CCK 1.6-1 and Views 1.6. I created a View to display my content type "calendar event" with the added field "datetime".
It is 7:52pm Arizona time, which is GMT -7; however, my calendar says the current date is tomorrow.
My stories post with the correct Arizona time.
I have tried many combinations of enabling/disabling "Configurable time zones" in Date and Time, and various settings of "Time Zone Handling" in my "datetime" field (which is in my content type "calendar event") -- but to no avail. Calendar still says tomorrow is current date.
Many thanks for any guidance!
staunton
Comments
maybe
don't know if the maintainer got the new dateapi in place, but in the meantime, http://drupal.org/node/99223#comment-631328 has helped some. before that, http://drupal.org/node/147386. worked for me, anyway.
hope it helps.
Success!
I used the patch described in http://drupal.org/node/99223#comment-631328 , and it worked! Today is highlighted as current date--and by this time in the day (even some hours earlier) the calendar had been showing tomorrow as current date.
tm, I light a candle to you. Thank you for taking the time to help me out.
Patch Help
I've tried to read on how to apply the match mentioned in the above post, but I can't seem to figure it out. Can anyone offer directions for installing the patch? I really appreciate all the help these boards are and thank you in advance!
dunno
i just stuck the replacement code directly into the file with a text editor, tested on a test site, and uploaded the revised file to production.
the handbook page for applying rolled patches is at http://drupal.org/node/60108.
Another Noob Question
Which file should I replace the code in? Date.module? I'm sorry I'm so dumb, but I'm slowly learning.
calendar_api.inc
if you are referring to the solution at http://drupal.org/node/99223#comment-631328, it would be calendar_api.inc in the calendar module. be sure to back up your files before doing this, just in case. also note that every time you update this module, this patch will have to be reapplied and tested.
keep an eye on the date module; if they get the date api updated to address this issue, this patch will no longer be needed.
good luck!
yes, that's correct
that's where I put the patch that fixed the problem: calendar_api.inc
Good luck from another newbie!
subscribe -- I've had this
subscribe -- I've had this bug since I first started using Drupal back in May -- I was hoping it was fixed in Drupal 5.6, but no.....