[Tickets #11976] Re: invation emails are handled wrong

Sun Jan 27 12:40:20 UTC 2013

BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE  
E-MAIL-ADRESSE WERDEN NICHT GELESEN.

Ticket-URL: http://bugs.horde.org/ticket/11976
------------------------------------------------------------------------------
  Ticket           | 11976
  Aktualisiert Von | jmozdzen at nde.ag
  Zusammenfassung  | invation emails are handled wrong
  Warteschlange    | Kronolith
  Version          | 4.0.3
  Typ              | Bug
  Status           | Feedback
  Priorität        | 1. Low
  Milestone        |
  Patch            |
  Zuständige       |
------------------------------------------------------------------------------

jmozdzen at nde.ag (2013-01-27 12:40) hat geschrieben:

Hi Jan,

> commit 41b7f1264814bcaa9207f0c1e4af1d456bbccc17
> Author: Jan Schneider <jan at horde.org>
> Date:   Sat Jan 26 13:44:25 2013 +0100
>
>     DTEND is non-inclusive.

I applied the change to my server and it does indeed correct the event  
display in IMP.

Unfortunately, it does not address the invalid modification of the  
stored event details:

--- cut here: event data before the event is accepted ---
Content-Type: application/x-vnd.kolab.event; name=kolab.xml
Content-Disposition: inline; x-kolab-type=xml; filename=kolab.xml
Content-Transfer-Encoding: quoted-printable

<?xml version=3D"1.0" encoding=3D"UTF-8"?>
<event version=3D"1.0">
   <uid>51051cde-17b0-45a1-ab3f-2805c0a86604</uid>
   <body>single-day all-day event Jan 28</body>
   <categories></categories>
   <creation-date>2013-01-27T12:26:06Z</creation-date>
   <last-modification-date>2013-01-27T12:27:30Z</last-modification-date>
   <sensitivity>public</sensitivity>
   <product-id>Horde_Kolab_Format_Xml-2.0.2 (api version: 1)</product-id>
   <summary>test event</summary>
   <location>test location</location>
   <start-date>2013-01-28</start-date>
   <alarm>15</alarm>
   <horde-alarm-methods>a:0:{}</horde-alarm-methods>
   <show-time-as>busy</show-time-as>
   <end-date>2013-01-28</end-date>
   <attendee>
     <display-name></display-name>
     <smtp-address>jmozdzen at nde.ag</smtp-address>
     <status>none</status>
     <request-response>false</request-response>
     <role>required</role>
   </attendee>
</event>
--- cut here ---

--- cut here: stored event details after the event was accepted ---
<?xml version=3D"1.0" encoding=3D"UTF-8"?>
<event version=3D"1.0">
   <uid>51051cde-17b0-45a1-ab3f-2805c0a86604</uid>
   <body>single-day all-day event Jan 28</body>
   <categories></categories>
   <creation-date>2013-01-27T12:26:06Z</creation-date>
   <last-modification-date>2013-01-27T12:29:37Z</last-modification-date>
   <sensitivity>public</sensitivity>
   <product-id>Horde_Kolab_Format_Xml-2.0.2 (api version: 1)</product-id>
   <summary>test event</summary>
   <location>test location</location>
   <start-date>2013-01-28</start-date>
   <alarm>15</alarm>
   <horde-alarm-methods>a:0:{}</horde-alarm-methods>
   <show-time-as>busy</show-time-as>
   <end-date>2013-01-29</end-date>
   <attendee>
     <display-name></display-name>
     <smtp-address>jmozdzen at nde.ag</smtp-address>
     <status>none</status>
     <request-response>false</request-response>
     <role>required</role>
   </attendee>
</event>
--- cut here ---

As you can see clearly, the <end-date> element was overwritten with  
the (false) exclusive end date from the invitation e-mail.

(Test case as originally reported - I created an event in my personal  
calendar and added me as the only invitee - the resulting event entry  
is listed above - then displayed the resulting invitation email in IMP  
(this time with correctly displayed end date) and clicked "accept and  
update in my calendar" - the resulting event entry contains the  
modified end date, as listed above).

Let me know if I can help out somehow, i.e. by tracing some code path  
in my installation.