phpGroupWare - Bugs: bug #10331, calendar can't handle dates before...
You are not allowed to post comments on this tracker with your current authentication level.
bug #10331: calendar can't handle dates before 1970
Submitter: | Matthias Leonhardt <mleonhardt> | ||
Submitted: | Thu 09 Sep 2004 07:27:40 AM UTC | ||
Category: | calendar | Item Group: | 0.9.16.003 |
Severity: | 3 - Normal | Priority: | 1 - Later |
Status: | Duplicate | Privacy: | Public |
Assigned to: | skwashd | Open/Closed: | Closed |
Component Version: | SVN | Operating System: | GNU/Linux - SuSE |
Reproducibility: | None | Planned Release: | 0.9.16.011+ |
Fixed Release: |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
CC list is empty
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 3 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2004-09-09 | skwashd | Status | None | Duplicate | |
Open/Closed | Open | Closed | |||
2004-09-09 | mleonhardt | Carbon-Copy | - | Added cboettger |
Powered by Savane 3.13-4b48.
Corresponding source code
second time, because this is really an issue of the calendar:
while syncing we use $this->bo_iCal->import($data_lines, true, $timestamp); to get new calendar-entries.
But if we have an entry (i.e. birthday) before 1970 the calendar can't handle this. php produces warnings: localtime doesn' support negative values.
perhapps you know a way to handle this.
I do have a birthday before 1970 and I can't really change that. If this birthday is present as a reminder date in any PDA/smart phone or Outlook (they all handle it the same way!) and the calendar is synchronized using SyncML, ALL birthday reminder for persons born before 1970 are pĆ¼laced on the day of the synchronization (actual date) in phpGW.
This has NOTHING to to with any addressbook entries. And it can't be changed in all other devices just to suit phpGW (BTW: the logic behind it is correct in all those other devices). So it's clearly a bug in phpGW calendar.