Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
Hello. I have a problem with the event's timezone show in Calendar view.
I'm working with Drupal 5.7, Date 2.0-rc, Calendar 2.0-rc and Views 1.6.
The thing is, when a look at the calendar, its shows the event time +5hours later. And when i look at the event node, its shows the correct time.
I disable the timezone configuration, to set the web timezone unique.
any help?
I now that the Calendar Module have many issues with the timezones, but i guess this will be easy to set right.
Another thins: If i change the view to any other kind, the hour of the event it's shows correctly.
Comments
Comment #1
zietbukuel CreditAttribution: zietbukuel commentedHaving the same issue, but in my case it display the hour -5.
Comment #2
millions CreditAttribution: millions commentedI'm having the same issue.
Comment #3
thomasmurphy CreditAttribution: thomasmurphy commentedsubscribing
Comment #4
millions CreditAttribution: millions commentedanyone figure out a solution? Raknu?
Comment #5
thomasmurphy CreditAttribution: thomasmurphy commentederr, yup, I changed my core timezone, which is in /admin/settings/date-time
mine was out of whack, for some reason. was applying the timezone when viewing a node but not when editing it.
Comment #6
millions CreditAttribution: millions commentednot doing anything for me. I tried US/Pacific, America/LosAngeles, America/Phoenix, US/Pacific-New, etc. They all have the time offset problem... any other suggestions?
Comment #7
millions CreditAttribution: millions commentedIt seems to only be an issue on events that have an end time or date. If you just show a starting time it's correct.
Comment #8
davidwhthomas CreditAttribution: davidwhthomas commentedsame problem here.
It does only seem to occur when an end-time is set.
Comment #9
vkr11 CreditAttribution: vkr11 commentedsubscribe
Comment #10
raknu CreditAttribution: raknu commentedI still have the same problem, even when i only set the start-time of the event.
I still haven't found a solution...
Comment #11
millions CreditAttribution: millions commentedKaren S, do you have any ideas? It's important for me to get this fixed! Thanks.
Comment #12
kimadactyl CreditAttribution: kimadactyl commentedI'm pretty sure this is a duplicate but I can't find something exactly the same. Me too, though. I'll look at this when I have a sec.
Comment #13
pvasener CreditAttribution: pvasener commentedsubscribing
Comment #14
KarenS CreditAttribution: KarenS commentedI'm working on the D6 version now, but a couple things will help debug this:
1) Update to the very latest Date module code -- use the dev version not the official release. There have been some fixes there that affect timezones.
2) Make sure you're not using the Event module -- there is a conflict between them right now where your timezone settings don't get saved in a way the Date module can access.
3) Update to the very latest Calendar module code -- the dev version, not the official release.
Clear all your caches out and try again.
If you still see problems after that, post an export of the view you're using and an export of the date field you're using.
Comment #15
pvasener CreditAttribution: pvasener commentedFor me, upgrading from the RC versions to the Dev ones (Calendar May 11 & Date May 16) corrected the bug.
Comment #16
ron_s CreditAttribution: ron_s commentedI've been waiting to upgrade to newer versions of Calendar and Date (in Drupal 5) until they are production-ready. However the timezone-related issues on our current site are becoming a bit unbearable. Any thoughts how how far away these are from production? Thanks.
Comment #17
raknu CreditAttribution: raknu commentedIt work's for me to. Just upgrade the calendar and date module to dev version.
Tank's KarenS ! ! !
Comment #18
jjohnsonBLC CreditAttribution: jjohnsonBLC commentedUgh, ignore me, I'm an idiot. I resolved my own problem related to this issue.
Comment #19
JohnAlbinSince raknu's problem is fixed by KarenS’s solution in #14, I'm marking this issue fixed.
Comment #20
Anonymous (not verified) CreditAttribution: Anonymous commentedAutomatically closed -- issue fixed for two weeks with no activity.