Tickets :: Comment on [#8645] Date import broken in turba

* Your Email Address
* Spam protection	Enter the letters below: .__ .__..___..__.\ / [__)\| \| _/ \| \| >< \| \\|__\./__.\|__\/ \
Comment	> 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.
Attachment
Watch this ticket