Answers.Body: <p>I know you said you checked the user's timezone but did you check the sitewide time zone in Drupal at /admin/config/regional/settings?</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-28T01:06:18.490Z
Answers.Text: Thank you, frTommy, that is already set correct as well... the Drupal site-wide timezone setting. Since "all of these settings" are still correct after the last daylight savings change, I wonder if the settings were incorrect before the change yet CiviCRM was not siting the error?
Answers.UserDisplayName: Michael Lueck
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-05-27T03:01:49.157Z
Answers.LastActivityDate: 2015-05-27T03:01:49.157Z
Answers.UserDisplayName: frTommy
Body: <p>I have been unable to get the CiviCRM warning about timezone settings corrected after this just past daylight savings transition. Usually I would correct it by changing the timezone setting of the Drupal user ID's. In the past, the user's timezone setting would be an hour off to the real time, so adjusting the timezone setting in Drupal back to current time always corrected the issue. However this time the user timezone setting already was correct.</p>
  
  <p>I have written up the following PHP tester:</p>
  
  <pre><code>&lt;?php
  
  $db = new mysqli('localhost', 'dbuserid', 'blablablapassword', 'db');
  
  if($db-&gt;connect_errno &gt; 0){
    die('Unable to connect to database [' . $db-&gt;connect_error . ']');
  }
  
  $sql = &lt;&lt;&lt;SQL
      SELECT NOW() AS `NOW`
  SQL;
  
  if(!$result = $db-&gt;query($sql)){
    die('There was an error running the query [' . $db-&gt;error . ']');
  }
  
  while($row = $result-&gt;fetch_assoc()){
    echo 'MySQLi date: ' . $row['NOW'] . '&lt;br /&gt;';
  }
  
  $result-&gt;free();
  
  echo 'PHP date: ' . date('Y-m-d H:i:s');
  
  ?&gt;
  </code></pre>
  
  <p>Which outputs:</p>
  
  <pre><code>MySQLi date: 2015-05-26 21:32:56
  PHP date: 2015-05-26 21:32:56
  </code></pre>
  
  <p>Looks like they match to me.</p>
  
  <p>I have also hard coded set the timezone into the Apache virtual site's configuration by adding to the site's .htaccess file:</p>
  
  <pre><code>  #Added PHP Timezone information to match Linux configuration
    php_value date.timezone "America/New_York"
  </code></pre>
  
  <p>Where else could be causing CiviCRM to complain thusly:</p>
  
  <pre><code>Environment Settings
  Timestamps reported by MySQL (eg "2015-05-26 21:28") and PHP (eg "2015-05-26 20:28" ) are mismatched.
  Read more about this warning
  </code></pre>
  
  <p>I am thankful,
  Michael</p>
  
Tags: <drupal><timezone>
Title: Why is CiviCRM not seeing the timezone correctly?
ThreadText: # Why is CiviCRM not seeing the timezone correctly?
  
  (Asked by: username_0 on 2015-05-27)
  
  I have been unable to get the CiviCRM warning about timezone settings corrected after this just past daylight savings transition. Usually I would correct it by changing the timezone setting of the Drupal user ID's. In the past, the user's timezone setting would be an hour off to the real time, so adjusting the timezone setting in Drupal back to current time always corrected the issue. However this time the user timezone setting already was correct.
  I have written up the following PHP tester:
  connect_errno > 0){
    die('Unable to connect to database [' . $db->connect_error . ']');
  }
  
  $sql = <<query($sql)){
    die('There was an error running the query [' . $db->error . ']');
  }
  
  while($row = $result->fetch_assoc()){
    echo 'MySQLi date: ' . $row['NOW'] . '';
  }
  
  $result->free();
  
  echo 'PHP date: ' . date('Y-m-d H:i:s');
  
  ?>
  
  Which outputs:
  MySQLi date: 2015-05-26 21:32:56
  PHP date: 2015-05-26 21:32:56
  
  Looks like they match to me.
  I have also hard coded set the timezone into the Apache virtual site's configuration by adding to the site's .htaccess file:
    #Added PHP Timezone information to match Linux configuration
    php_value date.timezone "America/New_York"
  
  Where else could be causing CiviCRM to complain thusly:
  Environment Settings
  Timestamps reported by MySQL (eg "2015-05-26 21:28") and PHP (eg "2015-05-26 20:28" ) are mismatched.
  Read more about this warning
  
  I am thankful,
  Michael
  
  **Tags:** drupal, timezone
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2015-05-27. Score: 3
  
  I know you said you checked the user's timezone but did you check the sitewide time zone in Drupal at /admin/config/regional/settings?
  
  > **Comments:**
  > **username_0**: Thank you, username_1, that is already set correct as well... the Drupal site-wide timezone setting. Since "all of these settings" are still correct after the last daylight savings change, I wonder if the settings were incorrect before the change yet CiviCRM was not siting the error?  
  
  ---
  
  