Answers.Body: <p>It turns out that if you are using Wordpress you need to set the timezone to specific location, e.g. London, rather than using the default UTC offset. When I used the London timezone the problem went away.</p>
  
  <p>Configure this in WordPress at <code>Settings &gt; General</code>  <code>/wp-admin/options-general.php</code></p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-09-05T04:01:32.493Z
Answers.Text: Thanks Marian, perfect answer for this trouble.
Answers.UserDisplayName: Ichi
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2018-03-20T21:32:07.400Z
Answers.LastActivityDate: 2018-10-15T18:05:04.850Z
Answers.LastEditDate: 2018-10-15T18:05:04.850Z
Answers.UserDisplayName: Marian Zastawny
Body: <p>I have a host running in a different time-zone from where I am operation and unless I set the website time zone to the hosting time zone I get the following error in CiviCRM:</p>
  
  <blockquote>
    <p>Timestamps reported by MySQL (eg "2018-03-07 12:20") and PHP (eg "2018-03-07 11:20" ) are mismatched.</p>
  </blockquote>
  
  <p>I know that my PHP time is correct, but how can I force the MySQL time to be set to my local time.</p>
  
  <p>I've looked through the available answers but most of them advise setting the website timezone to match the host time, which is suboptimal </p>
  
  <p>Is there anything that I can do to still be able to work in my time zone?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2018-03-16T14:13:16.550Z
Comments.Text: Have you seen these related questions?
  
  https://civicrm.stackexchange.com/questions/7527/timestamp-mismatch-between-mysql-and-php
  
  https://civicrm.stackexchange.com/questions/7586/does-the-timestamp-mismatch-error-cause-any-real-problems
Comments.UserDisplayName: William Mortada
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2018-03-19T18:08:36.217Z
Comments.Text: I discovered that when set the Time zone in Wordpress to London, rather than using UTC offset, the problem goes away.
Comments.UserDisplayName: Marian Zastawny
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2018-03-19T21:22:09.340Z
Comments.Text: That's great. You should post this as the answer to your question so that it helps others with the same problem.
Comments.UserDisplayName: William Mortada
Tags: <wordpress><error><mysql><php><timezone>
Title: timestamp mismatch
ThreadText: # timestamp mismatch
  
  (Asked by: username_0 on 2018-03-07)
  
  I have a host running in a different time-zone from where I am operation and unless I set the website time zone to the hosting time zone I get the following error in CiviCRM:
  
  > Timestamps reported by MySQL (eg "2018-03-07 12:20") and PHP (eg "2018-03-07 11:20" ) are mismatched.
  
  I know that my PHP time is correct, but how can I force the MySQL time to be set to my local time.
  
  I've looked through the available answers but most of them advise setting the website timezone to match the host time, which is suboptimal
  
  Is there anything that I can do to still be able to work in my time zone?
  
  **Tags:** wordpress, error, mysql, php, timezone
  
  > **Comments:**
  > **username_1**: Have you seen these related questions?  https://civicrm.stackexchange.com/questions/7527/timestamp-mismatch-between-mysql-and-php  https://civicrm.stackexchange.com/questions/7586/does-the-timestamp-mismatch-error-cause-any-real-problems  
  > **username_0**: I discovered that when set the Time zone in Wordpress to London, rather than using UTC offset, the problem goes away.  
  > **username_1**: That's great. You should post this as the answer to your question so that it helps others with the same problem.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2018-03-20. Score: 6
  
  It turns out that if you are using Wordpress you need to set the timezone to specific location, e.g. London, rather than using the default UTC offset. When I used the London timezone the problem went away.
  
  Configure this in WordPress at `Settings > General` `/wp-admin/options-general.php`
  
  > **Comments:**
  > **username_2**: Thanks username_0, perfect answer for this trouble.  
  
  ---
  
  