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.
On the month view of a custom calendar view containing simple nodes that a contain a CCK Date field with 'Time zone handling' set to Date's time zone, event times display in GMT, regardless of the timezone of the date. Changing the date field to use the site' timezone has no effect.
This is confusing for users who wish to see their events showing up in the proper time zone.
Comments
Comment #1
KarenS CreditAttribution: KarenS commentedThis is actually a bug in the date module. The timezone name is getting stored, but not the offset, so with no offset the date was displayed as if it was GMT. The method for displaying it in the node is different and there the problem with the offset wasn't showing up. At any rate, I'm moving this to the right queue and renaming it to reflect what it is.
Comment #2
moshe weitzman CreditAttribution: moshe weitzman commentedI *think* I am seeing a symptom of this problem. This time, my update #7 for date.install is failing with the error below:
Comment #3
moshe weitzman CreditAttribution: moshe weitzman commentedSo is it true that in the current release, site timezone preference is broken and to be avoided?
Comment #4
moshe weitzman CreditAttribution: moshe weitzman commentedoops - i meant the 'use date's timezone' choice for 'time zone handling'.
Comment #5
KarenS CreditAttribution: KarenS commentedI think this is partly related to a bug yched found in modules that alter columns based on their content. I'm postponing doing anything about this until I get the 5.2 version up and working, then I need to decide if I should just make those columns always available for all dates or not.
It's not timezone conversion so much that is not working, but the option to store date-specific timezones, which is the most complicated scenario of all the ways you can set things up. I'm very optimistic that the new version is going to clean up many or most of the timezone issues.
Comment #6
KarenS CreditAttribution: KarenS commentedFinally found the culprit here and committed a fix. There may be damage in the database from when the offsets were not saved, so there is an update to fix the database.
Comment #7
KarenS CreditAttribution: KarenS commentedComment #8
(not verified) CreditAttribution: commentedComment #9
drummdate_update_4000() in 4.7 is causing some trouble:
- No return value. At least do return array();
- 4.7.x can not handle non-sequential update numbers, so it should be 8 instead of 4000.
Comment #10
KarenS CreditAttribution: KarenS commentedI'm not making changes to the 5.1 version. I'm officially recommending you move to the 5.2 version now. If you have problems in that version you can check for existing issues or add new ones. Feature requests are now getting posted to the D6 version to be back-ported to 5.2.
This should not be an issue in 5.2.
Comment #11
igorik CreditAttribution: igorik commentedHi
I can confirm that this bug persist in the newes date module 5.2.1 and it is really confused on month calendar.
My events CCK time is e.g. 4 pm, but month calendar shows 2.pm
I am not sure but I think that it works some time ago with another date module version, some time before I manually added 2 hours more for offset to date module code because this bug (not very nice solution but it works).
Thanks
Igorik
http://www.somvprahe.sk
Comment #12
KarenS CreditAttribution: KarenS commentedYou need to do several things:
1) Make sure you emptied all the old code out of the date folder so you aren't unknowingly using some of the old files.
2) There could be old data stuck in caches after the upgrade, so edit your date fields and save them to clear those caches and edit and save your calendar to make sure it's cache is cleared.
3) If you manually altered a date somewhere, don't do that any more, there's no way to make it work if it's being altered.
Comment #13
KarenS CreditAttribution: KarenS commentedComment #14
igorik CreditAttribution: igorik commentedHi
I tried to do steps you suggest.
1) I delete module directories Date and calendar and copy newest module
2) I clear views cache but I can't edit date fields in appropriate nodes
(I tried one and I finish with this bug: http://drupal.org/node/304631)
when it will be fixed, I will be continued to finish rest steps you wrote.
Thanks
Igorik
http://www.somvprahe.sk
Comment #15
KarenS CreditAttribution: KarenS commentedIgorik, you can't have the original problem in this issue, that was for another version altogether. I think your problem is the other bug you posted, which indicates something is goofed up in your setup.
This issue is called 'date-specific timezone offset not getting saved', but I don't think that's what you're reporting anyway.
Anyway, concentrate on the other issue. Once that is working your other problems may go away.
Comment #16
Anonymous (not verified) CreditAttribution: Anonymous commentedAutomatically closed -- issue fixed for two weeks with no activity.