[Tickets #14197] Re: Nag_Driver_Kolab stores parent_id strings base64 encoded (should be: unencoded)

[noreply at bugs.horde.org]

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

Ticket URL: https://bugs.horde.org/ticket/14197
------------------------------------------------------------------------------
  Ticket             | 14197
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | Nag_Driver_Kolab stores parent_id strings base64
                     | encoded (should be: unencoded)
  Queue              | Kolab
  Type               | Bug
-State              | Feedback
+State              | Assigned
  Priority           | 1. Low
  Milestone          |
  Patch              |
-Owners             |
+Owners             | Michael Rubinsky
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2015-12-29 05:29) wrote:

Yup. This regression was introduced back in 2012 by:

https://github.com/horde/horde/commit/54173622945ca87ee48905bceb8b436c2e71d0af  
and is the result of Nag using internal ids as parent properties and  
not uids.

The patch looks good. Generally I would argue that code to perform the  
correction of the broken user data should be done in a login task.  
However, since it's conceivable that multiple Horde installs could be  
working against the same Kolab backend this is probably the safest way  
to handle it - with the caveat that the workaround will be removed in  
Horde 6.