Answers.Body: <p>Sorry for the delay but was I was able to solve my issue, I had set the time zone in WordPress > Settings > General and then changed from manual offset option to location based offset option. This is due to WordPress and CiviCRM handling time differently than WordPress when using the manual offset method.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-08-26T20:04:07.913Z
Answers.LastActivityDate: 2016-08-26T20:04:07.913Z
Answers.UserDisplayName: LJB
Answers.Body: <p>In testing i determined that all of the UTC offset TZ WordPress offers are invalid from a php perspective.   </p>
  
  <p>Set the timezone to the proper php TZ (Europe/Zurich for example) and that error will go away.   </p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-06-21T19:14:47.887Z
Answers.Text: Yes, if I am understanding you correctly. I had solved this issue and forgot to update this. What I had to do was in WordPress in Settings > General was change the Time Zone from using the Manual Offset option to a location based option. So in my case setting it to Timezone: New York made the error go away. I cannot locate the forum that eventually led me to this fix but it has something to with how WordPress changes the format of the time string and passes it to CiviCRM before changing it back to the standard format.
Answers.UserDisplayName: LJB
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-06-21T15:49:14.840Z
Answers.LastActivityDate: 2016-06-21T15:49:14.840Z
Answers.UserDisplayName: Kevin Cristiano
Answers.Body: <p>Perhaps clearing CiviCRM cache after changing it in the civicrm.settings.php file will fix it :)</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-22T23:30:18.610Z
Answers.Text: The precise question was "does anyone have any ideas?" My idea is that clearing the cache might fix it!
Answers.UserDisplayName: JohnFF
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-22T23:45:56.003Z
Answers.Text: That's fair.  At first read, it looked more like a comment, but I see your point.
Answers.UserDisplayName: Allen Hutchison
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-23T03:14:43.823Z
Answers.Text: maybe tweak to a 'suggestion' rather than a question ;-)
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-08-26T20:03:46.227Z
Answers.Text: Sorry for the delay but was I was able to solve my issue, I had set the time zone in WordPress > Settings > General and then changed from manual offset option to location based offset option. This is due to WordPress and CiviCRM handling time differently than WordPress when using the manual offset method.
Answers.UserDisplayName: LJB
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-03-22T22:05:54.573Z
Answers.LastActivityDate: 2016-03-23T10:43:00.810Z
Answers.LastEditDate: 2016-03-23T10:43:00.810Z
Answers.UserDisplayName: JohnFF
Body: <p>I have just done a new install of WordPress and CiviCRM, it has displayed this warning when looking at the CiviCRM dashboard:</p>
  
  <p>Environment Settings
  Timestamps reported by MySQL (eg "2016-03-22 14:45") and PHP (eg "2016-03-22 20:45" ) are mismatched.</p>
  
  <p>The link it refers to is this: <a href="https://wiki.civicrm.org/confluence/display/CRMDOC/checkMysqlTime" rel="nofollow">https://wiki.civicrm.org/confluence/display/CRMDOC/checkMysqlTime</a></p>
  
  <p>Which I have read but maybe I am missing something. </p>
  
  <p>I ran this command on MySQL "SELECT TIMEDIFF( NOW( ) , UTC_TIMESTAMP );"
  and it returns -06:00:00</p>
  
  <p>So then in my php.ini I set date.timezone=America/Chicago to match, then as another precaution I went to the WordPress wp-admin dashboard in the settings and set the timezone to UTC-6 and yet the warning is still displaying, does anyone have any ideas?</p>
  
Tags: <wordpress><installation><timezone>
Title: Environment Settings, mismatch timezone
ThreadText: # Environment Settings, mismatch timezone
  
  (Asked by: username_0 on 2016-03-22)
  
  I have just done a new install of WordPress and CiviCRM, it has displayed this warning when looking at the CiviCRM dashboard:
  
  Environment Settings
  Timestamps reported by MySQL (eg "2016-03-22 14:45") and PHP (eg "2016-03-22 20:45" ) are mismatched.
  
  The link it refers to is this: <https://wiki.civicrm.org/confluence/display/CRMDOC/checkMysqlTime>
  
  Which I have read but maybe I am missing something.
  
  I ran this command on MySQL "SELECT TIMEDIFF( NOW( ) , UTC\_TIMESTAMP );"
  and it returns -06:00:00
  
  So then in my php.ini I set date.timezone=America/Chicago to match, then as another precaution I went to the WordPress wp-admin dashboard in the settings and set the timezone to UTC-6 and yet the warning is still displaying, does anyone have any ideas?
  
  **Tags:** wordpress, installation, timezone
  
  
  ---
  
  ## 3 answers
  
  ### Answer by username_0 on 2016-08-26. Score: 2 | Accepted answer
  
  Sorry for the delay but was I was able to solve my issue, I had set the time zone in WordPress > Settings > General and then changed from manual offset option to location based offset option. This is due to WordPress and CiviCRM handling time differently than WordPress when using the manual offset method.
  
  
  ---
  
  ### Answer by username_1 on 2016-06-21. Score: 4
  
  In testing i determined that all of the UTC offset TZ WordPress offers are invalid from a php perspective.
  
  Set the timezone to the proper php TZ (Europe/Zurich for example) and that error will go away.
  
  > **Comments:**
  > **username_0**: Yes, if I am understanding you correctly. I had solved this issue and forgot to update this. What I had to do was in WordPress in Settings > General was change the Time Zone from using the Manual Offset option to a location based option. So in my case setting it to Timezone: New York made the error go away. I cannot locate the forum that eventually led me to this fix but it has something to with how WordPress changes the format of the time string and passes it to CiviCRM before changing it back to the standard format.  
  
  ---
  
  ### Answer by username_2 on 2016-03-22. Score: 0
  
  Perhaps clearing CiviCRM cache after changing it in the civicrm.settings.php file will fix it :)
  
  > **Comments:**
  > **username_2**: The precise question was "does anyone have any ideas?" My idea is that clearing the cache might fix it!  
  > **username_3**: That's fair.  At first read, it looked more like a comment, but I see your point.  
  > **username_4**: maybe tweak to a 'suggestion' rather than a question ;-)  
  > **username_0**: Sorry for the delay but was I was able to solve my issue, I had set the time zone in WordPress > Settings > General and then changed from manual offset option to location based offset option. This is due to WordPress and CiviCRM handling time differently than WordPress when using the manual offset method.  
  
  ---
  
  