| Summary | Kolab backend: Crash on parsing date fields |
| Queue | Turba |
| Queue Version | Git master |
| Type | Bug |
| State | Resolved |
| Priority | 1. Low |
| Owners | |
| Requester | thomas.jarosch (at) intra2net (dot) com |
| Created | 11/12/2012 (4631 days ago) |
| Due | |
| Updated | 11/22/2012 (4621 days ago) |
| Assigned | |
| Resolved | 11/22/2012 (4621 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Resolved
Bug #11736. The backend mayreturn "false" for optional data entries. Part of the problem is the
Kolab_Format library though. It could probably simply remove such
invalid dates from the resulting data array.
commit 2044351d27bd2a922d8da902d6c343cf13220fae
Author: Gunnar Wrobel <p@rdus.de>
Date: Tue Nov 20 09:36:10 2012 +0100
Do not bail out in case the Date value is 'false' because of an
unreadable date format. Should fix
Bug #11691.turba/lib/Driver/Kolab.php | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
http://git.horde.org/horde-git/-/commit/2044351d27bd2a922d8da902d6c343cf13220fae
<birthday>1960-11-22T23:00:00Z</birthday>
-> The other client writes out a datetime field instead of a plain date.
Still we shouldn't die on invalid data. It's better to log an error
once and be done with it.
Priority ⇒ 1. Low
Patch ⇒ No
Milestone ⇒
Queue ⇒ Turba
Summary ⇒ Kolab backend: Crash on parsing date fields
Type ⇒ Bug
State ⇒ Unconfirmed
parsing birthday fields from the server results in this crash:
[Mon Nov 12 16:57:41 2012] [error] [client 172.16.1.253] PHP Fatal
error: Call to a member function format() on a non-object in
/datastore/DEVEL/horde/turba/lib/Driver/Kolab.php on line 311,
referer:
https://172.16.1.123/horde/turba/contact.php?Horde=397lhne84v6q525rldd5ejhr21&source=4vKkDAhKP71Qjpi81hv17KA&key=mxstore%2800bf14a9-1ecc-4582-b1b9-613875b30bb0%29%3CeidFld%3A%3A%3C%28%29-0x0-0x0-0x0%3E%3CSE%3A0x201f04%3E%3CRK%3A450f27bf2735e449bc4f0316970a60a1%3E%3E
Thomas