[Tickets #13064] Re: Invalid DURATION for ALARM triggers
noreply at bugs.horde.org
noreply at bugs.horde.org
Mon Mar 24 21:14:42 UTC 2014
DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.
Ticket URL: http://bugs.horde.org/ticket/13064
------------------------------------------------------------------------------
Ticket | 13064
Updated By | marten at dmfs.org
Summary | Invalid DURATION for ALARM triggers
Queue | Kronolith
Version | Git master
Type | Bug
State | Feedback
Priority | 2. Medium
Milestone |
Patch |
Owners |
------------------------------------------------------------------------------
marten at dmfs.org (2014-03-24 21:14) wrote:
>>> Can you provide an event from the kronolith DB that triggers this?
>> You mean other than the exported VCALENDAR object?
>> How do can one get that?
>
> Via SQL dumps of the kronolith_events table. The event_id value
> should be take from the vcalendar object's id.
Sorry, I won't be able to provide a dump. I have to rely on the user
who reported it, but he didn't send any. I think you should be able to
reproduce the issue when you create an all-day event and set the alarm
to 8:00 on the day of the event (i.e. the alarm should fire after the
event started)
More information about the bugs
mailing list