| Summary | webdav deleting events |
| Queue | Kronolith |
| Queue Version | HEAD |
| Type | Bug |
| State | Resolved |
| Priority | 1. Low |
| Owners | jan (at) horde (dot) org |
| Requester | adrieder (at) sbox (dot) tugraz (dot) at |
| Created | 6/18/08 (6587 days ago) |
| Due | 6/18/08 (6587 days ago) |
| Updated | 7/7/08 (6568 days ago) |
| Assigned | 6/18/08 (6587 days ago) |
| Resolved | 7/7/08 (6568 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | 2.2.1 |
| Patch | No |
Taken from
State ⇒ Resolved
http://article.gmane.org/gmane.comp.horde.cvs/65849
State ⇒ Assigned
Assigned to Jan Schneider
New Attachment: sql.php.patch
We can savley remove the "else" statement since the one day gets added
anyway by listEventsConditional()
Priority ⇒ 1. Low
State ⇒ Unconfirmed
Patch ⇒ No
Milestone ⇒
Queue ⇒ Kronolith
Due ⇒ 6/18/08
Summary ⇒ webdav deleting events
Type ⇒ Bug
the kronolith database, because the api function _kronolith_list()
gets an empty event UID list.
The reason for this is, that the $endstamp is set to 9999/12/31 and in
the further processing 1 day is added to this date which caused the
year to be 10000.
The subsequent sql queries (mysql) with '10000-01-01 00:00:00' result
into an error.
One possible fix for this problem is to set the 'day' (or 'mday') to
30 in api.php:
$endstamp = new Horde_Date(array('year' => 9999, 'month' => 12, 'day' => 30));