From 740f91863b9a502ad5abe0a7a824265e069e0500 Mon Sep 17 00:00:00 2001 From: Ralf Becker Date: Tue, 15 Feb 2011 11:37:09 +0000 Subject: [PATCH] zpush seems to use a timestamp in utc (at least vcard backend does) for birthdays --- addressbook/inc/class.addressbook_activesync.inc.php | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/addressbook/inc/class.addressbook_activesync.inc.php b/addressbook/inc/class.addressbook_activesync.inc.php index d09fc62c8a..eb765fa8d2 100644 --- a/addressbook/inc/class.addressbook_activesync.inc.php +++ b/addressbook/inc/class.addressbook_activesync.inc.php @@ -325,8 +325,14 @@ class addressbook_activesync implements activesync_plugin_write, activesync_plug if (!empty($contact[$attr])) $message->$key = base64_encode($contact[$attr]); break; - case 'bday': // zpush uses timestamp in servertime - if (!empty($contact[$attr])) $message->$key = egw_time::to($contact[$attr],'server'); + case 'bday': // zpush seems to use a timestamp in utc (at least vcard backend does) + if (!empty($contact[$attr])) + { + $tz = date_default_timezone_get(); + date_default_timezone_set('UTC'); + $message->birthday = strtotime($contact[$attr]); + date_default_timezone_set($tz); + } break; case 'cat_id':