5

Every time I log in to CiviCRM I get the following error message:

Timestamps reported by MySQL (eg "2015-11-06 13:44") and PHP (eg "2015-11-06 11:44" ) are mismatched.

I am using CiviCRM 4.6.10 and Drupal 7.41.

The host (CiviHosting) has said that the MySQL server timezone is set to "Europe/Sofia" and can't be changed.

I have set the PHP timezone via php.ini to match this:

date.timezone = "Europe/Sofia"

However, I am still getting this error message.

The date section of phpinfo shows the following:

date/time support   enabled
"Olson" Timezone Database Version   2013.3
Timezone Database   internal
Default timezone    Europe/London

Directive   Local Value Master Value
date.default_latitude   31.7667 31.7667
date.default_longitude  35.2333 35.2333
date.sunrise_zenith 90.583333   90.583333
date.sunset_zenith  90.583333   90.583333
date.timezone   Europe/Sofia    Europe/Sofia

(Note that the 'Default timezone' is different to the 'date.timezone'.)

Any idea how I can fix this?

Thanks for your help.

Improve this question
1

5 Answers 5

Reset to default
2

I have flagged a similar problem with Joomla as an issue a long time ago and submitted some code to solve it:

https://issues.civicrm.org/jira/browse/CRM-15656

The CiviCRM team reckon it will be fixed in 4.7.7.

Improve this answer
3
  • That's great! I hope that fixes this problem.
    – William Mortada
    Apr 20, 2016 at 15:33
  • Wiliam - I just switched to CiviHosting and have run across the same problem - also in the UK. However, it doesn't seem to create a problem - so far that is... Did you ever find a fix for this?
    – Andy Clark
    Nov 22, 2017 at 9:29
  • @AndyClark Not really, other than to change the user's timezone to match - see civicrm.stackexchange.com/a/8222/127. However I'm not sure if it actually causes any problems.
    – William Mortada
    Nov 22, 2017 at 21:03
1

check what's the timezone under /admin/config/regional/settings, drupal can overwrite the php default timezone

Improve this answer
2
  • Thanks. I have tried changing that but it doesn't appear to make any difference. Also the organisation is based in the UK so want London to be the timezone for users.
    – William Mortada
    Nov 9, 2015 at 13:26
  • Changing the timezone for the user does seem to fix this problem (though not in a satisfactory way). See my answer below for details.
    – William Mortada
    Dec 14, 2015 at 21:04
1

This is one possible solution.

https://beta.suresupport.com/faq/article-1568/en/setting_mysql_session_time_zone

Another is setting the 'timezone' property in php.ini or .htaccess file, or in civicrm.settings.php or drupal's settings.php

Improve this answer
3
  • Thanks for the link but I'm not clear how I could use this. Are you suggesting I edit the core CiviCRM files?
    – William Mortada
    Nov 9, 2015 at 13:29
  • As mentioned in my question I have edited the php.ini file.
    – William Mortada
    Nov 9, 2015 at 13:30
  • Looking at the source code for CiviCRM it looks like it sets the MySQL timezone as part of the initialisation process anyhow. (See setMySQLTimeZone() function in CRM/Utils/System/Base.php)
    – William Mortada
    Nov 10, 2015 at 13:10
1

As an experiment, I edited your CRM/Utils/System/Base.php file and changed:

      $sql = "SET time_zone = '$timeZoneOffset'";

to

      $sql = "SET time_zone = 'Europe/London'";

and that seems to have fixed the problem. This is certainly not the ideal solution, but it does work.

Improve this answer
1
  • Unfortunately that doesn't help. I still get the same error when I log in.
    – William Mortada
    Dec 9, 2015 at 17:31
1

I have discovered that if I change the timezone for my Drupal user account to 'Europe/Sofia' then I no longer get this error message.

This solves the problem, but not in a very satisfactory way as I'm based in the UK and would like the timezone for my user to reflect this.

It appears that CiviCRM creates this error message if your Drupal user account isn't in the same timezone as the database server.

I'm still not sure if this actually causes any real problems. See my related post: Does the 'timestamp mismatch' error cause any real problems?

Improve this answer

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.