[Tickets #3965] Re: Track the Organizer of events

[noreply at bugs.horde.org]

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

Ticket-URL: https://bugs.horde.org/ticket/3965
------------------------------------------------------------------------------
  Ticket           | 3965
  Aktualisiert Von | lang at b1-systems.de
  Zusammenfassung  | Track the Organizer of events
  Warteschlange    | Kronolith
  Version          | Git master
  Typ              | Enhancement
  Status           | Accepted
  Priorität        | 2. Medium
  Milestone        |
  Patch            |
  Zuständige       | Ralf Lang (B1 Systems GmbH), Horde Developers
------------------------------------------------------------------------------


lang at b1-systems.de (2015-01-10 10:19) hat geschrieben:

https://github.com/horde/horde/pull/118

I have a solution which sort of works for my scenario:

Google calendar invites horde user, horde user accepts via  
thunderbird, thunderbird uses horde as caldav backend.

Previously, Horde dropped the ORGANIZER and used the CREATOR (the  
accepting user) as the ORGANIZER when re-exporting the event to Caldav  
-> thunderbird.
Also exports the ORGANIZER when exporting the event to ICS via  
Kronolith Dynamic UI.

SHOULD also work for ActiveSync, but I have not done much testing on this.

The ORGANIZER attribute is currently not exposed in toJSON and it's  
not displayed anywhere.

Please review.

ActiveSync users: Please test.