3

I hope I have a strange, but straight forward issue -- there's a 1 hour offset SOMETIMES in the created_date field in civicrm_contact table, and what gets outputted in a CiviCRM report (see the attached images).

MySQL is set to use SYSTEM time as well as PHP - ie, and no timezone conflict.

Any suggestions would be greatly appreciated. We are using Drupal 7 + CiviCRM 4.6.

Time in MYSQL

Time in Detailed Member Report

3
  • what is your users timezone setting in drupal?
    – petednz - fuzion
    Nov 26, 2015 at 0:13
  • It's strange, both were set to Eastern (-4). However, when I switched my timezone to UTC (0) in Drupal, the timestamps were displayed as expected, but now we have that PHP/MySQL timestamp mismatch warning. I also noticed the created_date is set as "TIMESTAMP" in the database, but the format is clearly DATETIME -- is there a reason for this? Nov 26, 2015 at 20:07
  • really not sure sorry
    – petednz - fuzion
    Nov 26, 2015 at 23:59

2 Answers 2

1

It's a timezone issue. Your database and drupal timezone must be same. Sometime it's happen due to Daylight saving time.

0

In case anyone has the same version (4.6.7), this was the fix for our issue - Drupal timezone code does not handle UTC correctly - https://github.com/civicrm/civicrm-core/pull/6576

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.