Answers.Body: <p>[UPDATE - IS FIXED]  </p>
  
  <p>I fixed this by revisiting WordPress's settings and changing the Timezone setting from "UTC -5" to "Chicago".  Both of these settings reflect the same time zone, so why these two settings are seen as different I can't say, but Civi no longer complains. </p>
  
  <p>So I guess the lesson is: if you want to get rid of this error and you're showing no actual disagreement on timezone between the server, PHP or WordPress, go to WordPress and pick the timezone that is named for the city you're aiming at.</p>
  
  <p>Hope that helps someone.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-08-23T18:55:15.943Z
Answers.LastActivityDate: 2018-08-23T18:55:15.943Z
Answers.UserDisplayName: Harrumph
Body: <p>I see a lot of related questions, but none that quite handle the following:</p>
  
  <p>System: Ubuntu/Wordpress 4.9.8  Civi 4.7.23</p>
  
  <p>I'm about to upgrade Civi but the error about "Timestamp mismatch" is making me worry.</p>
  
  <p>The MySQL time stamp is correct and matches "date" on the server.</p>
  
  <p>The Wordpress time setting is correct and matches "date" on the server.</p>
  
  <p>The PHP time setting as exposed in phpinfo() is correct although it of course doesn't spell out a time, just a timezone, which is correct.</p>
  
  <p>So why is this error persisting?</p>
  
Tags: <timestamp>
Title: How do I eliminate the error "Timestamp Mismatch"?
ThreadText: # How do I eliminate the error "Timestamp Mismatch"?
  
  (Asked by: username_0 on 2018-08-21)
  
  I see a lot of related questions, but none that quite handle the following:
  
  System: Ubuntu/Wordpress 4.9.8 Civi 4.7.23
  
  I'm about to upgrade Civi but the error about "Timestamp mismatch" is making me worry.
  
  The MySQL time stamp is correct and matches "date" on the server.
  
  The Wordpress time setting is correct and matches "date" on the server.
  
  The PHP time setting as exposed in phpinfo() is correct although it of course doesn't spell out a time, just a timezone, which is correct.
  
  So why is this error persisting?
  
  **Tags:** timestamp
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2018-08-23. Score: 1
  
  [UPDATE - IS FIXED]
  
  I fixed this by revisiting WordPress's settings and changing the Timezone setting from "UTC -5" to "Chicago". Both of these settings reflect the same time zone, so why these two settings are seen as different I can't say, but Civi no longer complains.
  
  So I guess the lesson is: if you want to get rid of this error and you're showing no actual disagreement on timezone between the server, PHP or WordPress, go to WordPress and pick the timezone that is named for the city you're aiming at.
  
  Hope that helps someone.
  
  
  ---
  
  