Tickets :: Comment on [#7470] Sunbird/Lightning alarm dismissal and snooze incompletely implemented

* Your Email Address
* Spam protection	Enter the letters below: .___. ..__..___..__ [__ \|\ \|\| \| \| [__) \| \| \\|\|__\ \| [__)
Comment	>> can you clarify the situation where the Driver patch breaks? > > > > Horde_Alarm has been added with Horde 3.2. But we maintain backward > compatibility in all H3 applications with any Horde 3.x version, i.e. > also with Horde versions before 3.2. Thus you can't simply assume > that Horde_Alarm exists in Kronolith code. > > Beside that, since I implemented the iCalendar patch differently, the > Kronolith patch has to be updated to reflect that. > > > >> It seems to me if you are subscribed read-write to a calendar and > >> then add an alarm in the external application that it should > >> overwrite any alarm in the database for that event. In addition, if > >> you remove an alarm it should remove it from the database. > > > > Exactly, and this already happens, e.g. in > Kronolith_Driver_sql::deleteEvent(). You can use the Horde_Alarm > handling there as a blueprint for your own changes in the snoozing > code. > > > >> The situation where one is subscribed to the calendar via ics, > >> perhaps in Sunbird, and the calendar is updated in kronolith and then > >> sent from Sunbird prior to downloading changes from kronolith is one > >> that is impossible to handle with the current version of Sunbird > >> because it doesn't have any sense of an offline cache or validation > >> of changes over webdav. Whoever writes last always wins in that > >> scenario. > > > > Yes, but that has nothing to do with this request anyway.
Attachment
Watch this ticket

Saved Queries