Answers.Body: <p>For us, there were a couple of changes that made this to work. First, in the database, the civicrm activity_date_time type was modified to be a timestamp. This made it so that when CiviCRM saved the date and time it was stored in the database as UTC once the Drupal timezone was also set to UTC (but users are able to select their own timezone and it behaves appropriately). According to developers in the CiviCRM IRC, this change can be made for any CiviCRM date time type. We also set our OS time to UTC. With just these changes, the Calendar View was still not displaying correctly because it was being adjusted twice. To fix that, we set tz_handling to 'none' in the function civicrm_date_views_fields in civicrm.views.inc.</p>
  
  <p>Hope it helps somebody else!</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-01-04T15:43:16.067Z
Answers.LastActivityDate: 2016-01-04T15:43:16.067Z
Answers.UserDisplayName: Cheryl
Body: <p>We were running into issues with how CiviCRM activities are showing in Drupal Calendar (Views). Drupal is adjusting the provided activity date/time based on the user configured time zone. For us, this is desired behavior because we have users crossing multiple time zones who want to see the time the activity is executed in whatever time zone they are in.</p>
  
  <p>After a little research (and finding these threads:
  <a href="https://issues.civicrm.org/jira/browse/CRM-9683" rel="nofollow noreferrer">https://issues.civicrm.org/jira/browse/CRM-9683</a>,<br>
  <a href="https://forum.civicrm.org/index.php/topic,23411.msg98329.html#msg98329" rel="nofollow noreferrer">https://forum.civicrm.org/index.php/topic,23411.msg98329.html#msg98329</a>, 
  <a href="https://civicrm.stackexchange.com/questions/7283/what-timezones-should-we-use-on-the-server-and-database/7293">What timezones should we use on the server and database?</a>, though there are many more tangentially related ones)
   it appears that CiviCRM assumes that all users will be in the same timezone and stores activity date/times as the local time into the database. Drupal expects that the stored times are in UTC, hence our issue. Would a "simple" fix of converting the activity datetime column format to a timestamp format in mysql be a reasonable fix? I'm worried that we're going to run into this in multiple places...</p>
  
  <p>Thanks!</p>
  
  <p>As an aside, I think it would make sense as a future change for CiviCRM to respect the Drupal user configurable time zones.</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2015-12-22T17:08:30.433Z
Comments.Text: I have a somewhat related question (also with a bounty!): http://civicrm.stackexchange.com/questions/7586/does-the-timestamp-mismatch-error-cause-any-real-problems
Comments.UserDisplayName: William Mortada
Tags: <activities><timezone>
Title: How are timezones handled in CiviCRM?
ThreadText: # How are timezones handled in CiviCRM?
  
  (Asked by: username_0 on 2015-12-10)
  
  We were running into issues with how CiviCRM activities are showing in Drupal Calendar (Views). Drupal is adjusting the provided activity date/time based on the user configured time zone. For us, this is desired behavior because we have users crossing multiple time zones who want to see the time the activity is executed in whatever time zone they are in.
  
  After a little research (and finding these threads:
  <https://issues.civicrm.org/jira/browse/CRM-9683>,  
  <https://forum.civicrm.org/index.php/topic,23411.msg98329.html#msg98329>,
  [What timezones should we use on the server and database?](https://civicrm.stackexchange.com/questions/7283/what-timezones-should-we-use-on-the-server-and-database/7293), though there are many more tangentially related ones)
  it appears that CiviCRM assumes that all users will be in the same timezone and stores activity date/times as the local time into the database. Drupal expects that the stored times are in UTC, hence our issue. Would a "simple" fix of converting the activity datetime column format to a timestamp format in mysql be a reasonable fix? I'm worried that we're going to run into this in multiple places...
  
  Thanks!
  
  As an aside, I think it would make sense as a future change for CiviCRM to respect the Drupal user configurable time zones.
  
  **Tags:** activities, timezone
  
  > **Comments:**
  > **username_1**: I have a somewhat related question (also with a bounty!): http://civicrm.stackexchange.com/questions/7586/does-the-timestamp-mismatch-error-cause-any-real-problems  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2016-01-04. Score: 4 | Accepted answer
  
  For us, there were a couple of changes that made this to work. First, in the database, the civicrm activity\_date\_time type was modified to be a timestamp. This made it so that when CiviCRM saved the date and time it was stored in the database as UTC once the Drupal timezone was also set to UTC (but users are able to select their own timezone and it behaves appropriately). According to developers in the CiviCRM IRC, this change can be made for any CiviCRM date time type. We also set our OS time to UTC. With just these changes, the Calendar View was still not displaying correctly because it was being adjusted twice. To fix that, we set tz\_handling to 'none' in the function civicrm\_date\_views\_fields in civicrm.views.inc.
  
  Hope it helps somebody else!
  
  
  ---
  
  