Fri, 10 Apr 2026 19:46:49 +0000 https://bugs.horde.org/ticket/8645 Date import broken in turba When trying to perform an address book import from CSV file in turba, the date import does not work for importing birthdays. I've tried with both an export from thunderbird, an excel file and with an export from horde's turba itself. I can match up all pairs of data in the import screen, when I go to process the import it detects that I have a birthday to import and asks for the date format. I confirm the correct format and separator, but after 'successful' import, the entry for the person has this:- First Name Pebbles Last Name Flintstone Middle Names Name Prefixes Name Suffixes Name Pebbles Flintstone Alias Birthday Wed, Dec 31, 69 Email janedoe@world.ca Home Phone 743 5521 Work Phone 748 7474 Mobile Phone 732 5521 Fax Pager The birthday is Dec31,69 ... suspiciously close to the epoch!! Thu, 15 Oct 2009 21:36:49 +0000 https://bugs.horde.org/ticket/8645#t56323 How was this csv file generated? Shouldn't the DOB field contain a 4 digit year? Thu, 15 Oct 2009 23:23:34 +0000 https://bugs.horde.org/ticket/8645#t56324 I tried with a full 4 digit year first, that did exactly the same thing. I changed the year to 2 digits since the turba import date format window only indicates 2 digit years. Either way, the date import doesn't work. I tried 4 digit years, dates created from excel, dates exported from turba and dates exported from thunderbird custom field. Fri, 16 Oct 2009 01:38:39 +0000 https://bugs.horde.org/ticket/8645#t56325 I can import this file perfectly fine with the latest Turba version. Mon, 26 Oct 2009 14:19:16 +0000 https://bugs.horde.org/ticket/8645#t56397 > I can import this file perfectly fine with the latest Turba version. Which version is that? I'm using H3 2.3.2. I just tried again and it certainly displays the Birthday as the wrong date. I did a mysql dump of the database in use and the field object_bday contains the value 94-2-18. So looks like the actual import gets what is there, but is it storing it in the correct format to allow the display to come out right? Mon, 26 Oct 2009 15:12:03 +0000 https://bugs.horde.org/ticket/8645#t56402 It's stored as 1994-02-18 here. What database backend do you use? Mon, 26 Oct 2009 15:18:00 +0000 https://bugs.horde.org/ticket/8645#t56403 > It's stored as 1994-02-18 here. What database backend do you use? # MySQL # Server version: 5.0.51a-3ubuntu5.4-log # Protocol version: 10 # MySQL charset: UTF-8 Unicode (utf8) Web Server: Apache/2.2.8 (Ubuntu) DAV/2 SVN/1.4.6 mod_ssl/2.2.8 OpenSSL/0.9.8g PHP/5.2.11 MySQL client version: 5.0.51a PHP extension: mysqli Mon, 26 Oct 2009 15:35:09 +0000 https://bugs.horde.org/ticket/8645#t56405 FWIW, I'm also getting the incorrect results (with both 2 digit and 4 digit years), and also use mySQL Mon, 26 Oct 2009 18:42:21 +0000 https://bugs.horde.org/ticket/8645#t56420 Trying to solve this - the date is being stored in the db as 94-2-18 both in Git and in FW_3, but in Git, Horde_Date is able to handle that as input and correctly parse the date. In FW_3, Horde_Date chokes on that value as input. If I change the year to 1994 in the original file, it gets stored as 1994-2-18, but FW_3 still has trouble with it due to the single digit month. I can't find where it is loosing (or not receiving) the proper MM format. I've traced the import process all the way from turba to Horde_Data and back again, and all through the code the year maintains a YY format, while the month retains a single digit format. Sat, 13 Feb 2010 22:28:03 +0000 https://bugs.horde.org/ticket/8645#t57984 Changes have been made in CVS for this ticket: make sure month and day are 0 padded. Fixes Bug: 8645 http://cvs.horde.org/diff.php/framework/Data/Data.php?rt=horde&r1=1.80.10.19&r2=1.80.10.20&ty=u Sun, 09 May 2010 18:44:06 +0000 https://bugs.horde.org/ticket/8645#t58743 Fixed. We were not zero padding the month and day strings being returned from Horde_Data::mapDate(). The import will still require the source file to contain 4 digit years. Sun, 09 May 2010 18:46:05 +0000 https://bugs.horde.org/ticket/8645#t58744 Moving to framework queue since this was a fix in Horde_Data Sun, 09 May 2010 18:46:45 +0000 https://bugs.horde.org/ticket/8645#t58745