Closed (outdated)
Project:
Event
Version:
6.x-2.x-dev
Component:
Date Picker
Priority:
Critical
Category:
Support request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
12 Jan 2010 at 02:12 UTC
Updated:
13 Apr 2018 at 21:01 UTC
Jump to comment: Most recent
Comments
Comment #1
gerhard killesreiter commentedcan you provide information about your server settings, the php version you use, and the exact event.module settings?
Comment #2
mcannell commentedI'll try:
Under Administer::Events::Event overview
Upcoming event block limit: 6
Default overview: Month
Table view default period: 30
Taxonomy filter controls: Never show taxonomy filter control
Content type filter controls: Never show content type filter control
Under Administer::Events::Timezone handling
Event time zone input: Use the sitewide time zone
Event time zone display: Use the sitewide time zone
Time notation preference: 12h
(If this is not what you mean by event.module settings, please specify where I get the info you need)
I'm using
linux
Apache 2.2.14
Mysql 5.1.43
php 5.2.11
Comment #3
gerhard killesreiter commentedWhat is the timezone setting at admin/settings/date-time ?
Can you execute the following SQL query and paste the results?
Select * from variable where name like 'event_%';
Select timezone_id, timezone from users where uid = X;
(replace X with your user ID)
Comment #4
mcannell commentedDefault Time Zone: America/New_York
User-configurable time zones: Enabled (Disabled doesn't change anything)
First day of week: Sunday
Results of SQL query
timezone_id: 0
timezone: NULL
Comment #5
mcannell commentedany help on this?
Comment #6
alistair.boudreaux commentedI am running into the same issue. Has there been a fix?
Comment #7
arcaicI am also getting this issue? 5 hours added to the times I enter. Time zone is UK/London.
I get the issue when displaying event start dates in a custom view. I get it if I use standard or custom date formats.
The event times are displayed correctly in the calendar though.
Do you need any more information?
Andy
Comment #8
MafiaMoe commentedThis is a semi update: I have noticed this issue when using this and other modules as well. The temporary fix for other modules is to actually remove the setting for the server time from Drupal completely. This has potentially severe side effects of course, which in my case actually damages the event module functionality. Events show in upcoming events but do not work when viewing or editing the date. It shows "Start: 00/00/" on the node page and "January - 00 - (blank) (blank) : (blank) am" when editing. I only did this as there was simply no other way around it with the other modules.
If you can, you might try changing the time zone of the server until it saves and displays correctly. This may also be a bigger issue with another module.
This all seems to connected to not be centered around the same set of bugs, or else I would have made a new issue.
Here is an example: http://www.asmeucm.org/node/75
Comment #9
wildlife commentedAny solution to this yet? I've been having the same thing for months. It is a royal pain to have to remember to set the time 5 hours before the event EVERY time I have to go in to edit an event in any way. I now am working on a project where we will have dozens of partners creating events, and this will be entirely unacceptable to the people I'm doing the site for, so I have to have this matter solved before I can present the events/calendar functionality I'm building. So any further input on this would be very much appreciated.
Comment #10
wildlife commentedFound the solution!
Content Management
| Content Types
| Edit Event (or whatever content type you have your date field in)
| Manage Fields
| Date
In the page that opens to edit your Date field configuration, look for a dropdown that is labeled
Time zone handling:
Set that to No time zone conversion.
That works for my needs. It may throw off things if you want time zone offsets for users in other time zones, but that's not needed with the site I'm working on.
Hope this helps you and others experiencing this problem.
Comment #11
jenifertucker commentedThanks for the tip wildlife - did the trick after a long time trying to fathom this out.
Comment #12
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.