[Tickets #11563] Re: Small display glitch after creating new tag

[noreply at bugs.horde.org]

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

Ticket URL: https://bugs.horde.org/ticket/11563
------------------------------------------------------------------------------
  Ticket             | 11563
  Updated By         | Git Commit <commits at lists.horde.org>
  Summary            | Small display glitch after creating new tag
  Queue              | Nag
  Version            | Git master
  Type               | Bug
  State              | Assigned
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Horde Developers, Michael Rubinsky
------------------------------------------------------------------------------


Git Commit <commits at lists.horde.org> (2016-02-04 22:10) wrote:

Changes have been made in Git (master):

commit bdb81d130c9bb88d2c91e245df8bb4511822430a
Author: Michael J Rubinsky <mrubinsk at horde.org>
Date:   Thu Feb 4 17:06:36 2016 -0500

     Bug: 11563  Fix adding tags when using Kolab.

     Kolab doesn't use the UID generated by Nag_Driver::add(), but
     calculates it after, so we need to overwrite the UID that we send
     to the tagger, or else it is tagged with the incorrect UID.

     This was causing the kolab object to not be completly tagged until
     the backend was synced with Horde again - essentially creating
     orphaned rampage_object entries with the incorrect UID.

  nag/lib/Driver/Kolab.php |    1 +
  1 files changed, 1 insertions(+), 0 deletions(-)

http://github.com/horde/horde/commit/bdb81d130c9bb88d2c91e245df8bb4511822430a