[Tickets #14249] catch exception of a recurring event where base event no longer is a recurring event

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: https://bugs.horde.org/ticket/14249
------------------------------------------------------------------------------
  Ticket             | 14249
  Created By         | michael.menge at zdv.uni-tuebingen.de
  Summary            | catch exception of a recurring event where base event
                     | no longer is a recurring event
  Queue              | Kronolith
  Version            | 4.2.11
  Type               | Bug
  State              | Unconfirmed
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


michael.menge at zdv.uni-tuebingen.de (2016-02-11 08:51) wrote:

Quoting my mail and Jans reply to kronolith mailinglist:
http://permalink.gmane.org/gmane.comp.horde.kronolith/7056

>> one of our users has tries to accept and add an event received via  
>> iCal invitation mail.
>> This action failed with the following error in Kronolith 4.2.11
>>
>> call to a member function addException() on a non-object in  
>> /var/www/html/horde/kronolith
>> /lib/Event.php on line 1447, referer: https://webmail.uni-tuebingen.de
>> /imp/dynamic.php?page=mailbox

....
>> 4. should Kronolith catch this error?
>
> Yes. This may happen if we come across an exception of a recurring   
> event, and can find the base event, but that base event no longer is  
> a  recurring event