Fri, 10 Apr 2026 09:50:17 +0000 https://bugs.horde.org/ticket/3741 monthdayyear field for birthday before 1970-01-01 Maybe after installing the latest Horde & Turba updates, the birthday field can't save dates before 1970-01-01. This worked before... I included mozillaAbObsoletePerson as schema for my OpenLDAP server and added in config/sources.php 'birthday' => 'mozillaCustom2' The LDAP browser shows for a date after 1970-01-01 # slapcat | grep custom2 1978-05-26 => mozillaCustom2: 1978-05-26 00:00:00 That's fine. But a date before 1970-01-01 doesn't work: 1938-05-26 => mozillaCustom2: 1969-12-31 00:00:00 Any idea? I've tried: $attributes['birthday'] = array( 'label' => _("Birthday"), 'type' => 'monthdayyear', 'required' => false, 'params' => array(1900), 'required' => false ); and $attributes['birthday'] = array( 'label' => _("Birthday"), 'type' => 'monthdayyear', 'required' => false, 'params' => array(1900, null, true, '%Y-%m-%d'), 'required' => false ); and $attributes['birthday'] = array( 'label' => _("Birthday"), 'type' => 'monthdayyear', 'required' => false, 'params' => array(1900, null, true, '%Y-%m-%d 00:00:00'), 'required' => false ); The result is allways the same Thu, 06 Apr 2006 10:05:42 +0000 https://bugs.horde.org/ticket/3741#t18624 Works fine with the following setting for the sql driver, it has to be an issue with the ldap driver: $attributes['birthday'] = array( 'label' => _("Birthday"), 'type' => 'monthdayyear', 'params' => array(1900, null, true, '%Y-%m-%d'), 'required' => false, ); Sat, 08 Apr 2006 09:40:34 +0000 https://bugs.horde.org/ticket/3741#t18677 I found the code that causes this problem. It's inside horde/lib/Horde/date.php The function timestamp() { return MakeTime($this->hour, $this->min, $this->sec, $this->month, $this->mday, $this->year); } Returns a wrong value for dates before 1970-01-01 System Debian Sarge 3.1 with PHP Version 4.3.10-16 Resolution could be: http://www.php.net/mktime#38068 For me, this works. Ralph Mon, 01 May 2006 11:51:58 +0000 https://bugs.horde.org/ticket/3741#t19616 That's indeed a nice solution, independently from this specific bug. Mon, 01 May 2006 12:12:46 +0000 https://bugs.horde.org/ticket/3741#t19619 > Resolution could be: > http://www.php.net/mktime#38068 This does not work for every date! There are discrepancies from 1 day for some dates. The "adodb_date_time_library" seems to be a better solution for working with dates befor 1.1.1970: http://www.xaraya.com/documentation/phpxref/xaradodb/adodb-time.inc.php.source.txt Still testing ... Ralph Mon, 01 May 2006 21:08:09 +0000 https://bugs.horde.org/ticket/3741#t19628 Any further testing results? Thu, 18 May 2006 15:48:26 +0000 https://bugs.horde.org/ticket/3741#t20346 I've had this bug on two servers which are both under Debian Sarge 3.1 stable. Nearly the same configuration and the same bug. The "adodb_date_time_library" solultion works for both machines. Thu, 18 May 2006 15:55:43 +0000 https://bugs.horde.org/ticket/3741#t20347 PHP 5.1 makes this just work. So I'm less inclined to work on workarounds. Any other opinions here? Mon, 22 May 2006 04:16:20 +0000 https://bugs.horde.org/ticket/3741#t20462 > PHP 5.1 makes this just work. Even on Windows? Mon, 22 May 2006 07:38:13 +0000 https://bugs.horde.org/ticket/3741#t20471 Yup - that's where I was testing on the plane. I didn't explicitly test dates after 2038, but dates around 1925 work fine. Mon, 22 May 2006 15:50:40 +0000 https://bugs.horde.org/ticket/3741#t20489 Good to know. But I think it would still be nice to have support for these dates before Horde 4. Mon, 22 May 2006 16:22:08 +0000 https://bugs.horde.org/ticket/3741#t20490 ...with PHP 4 actually. Mon, 22 May 2006 16:22:40 +0000 https://bugs.horde.org/ticket/3741#t20491 Sure... but how do you want to do that? Use Horde_Date everywhere? Did we have Horde_Date in Horde 3.0.0? We'd have to update all of the code for dealing with timestamps to use a hack like adodb's functions. Mon, 22 May 2006 16:32:02 +0000 https://bugs.horde.org/ticket/3741#t20492 > Did we have Horde_Date in Horde 3.0.0? Yes, and we use it all around in Kronolith. That means that we can use it at least in Horde_Date internally in any other framework packages which would help the original issue of this ticket. Mon, 22 May 2006 21:16:07 +0000 https://bugs.horde.org/ticket/3741#t20501 Okay, fallback added as Horde_Date::_mktime, used in Horde_Date::timestamp Thu, 14 Jun 2007 03:53:23 +0000 https://bugs.horde.org/ticket/3741#t34070