[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 | michael at brohl.net
  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
------------------------------------------------------------------------------


michael at brohl.net (2015-12-16 14:11) hat geschrieben:

I won't classify this as new functionality, it's a serious bug and  
very annoying.
Customers already started to apply filter rules to sort out false event mails.

I would very much appreciate a bugfix / patch for the 5.2 Releases.

>
>> Does anyone already tested the patch in FRAMEWORK_5_2 branch. The
>> patch shows some "Hunk #? FAILED at ???" messages, but it should not
>> to be hard to fix the patch for FRAMEWORK_5_2.
>
> No. It won't be back-ported to FW_5_2.  Since this is new  
> functionality, it won't be available in a stable release until Horde  
> 6.
>
>> After testing I may want to revert the patch. Is it enough to revert
>> the patch and to remove event_organizer from table kronolith_events
>> (from kronolith/migration/26_kronolith_remote_organizer.php)?
>
> You should use the horde-db-migration script to migrate down to 25.