[Tickets #14199] Re: Decoding of base64 encoded Kolab (.xml) objects is broken

[noreply at bugs.horde.org]

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

Ticket URL: https://bugs.horde.org/ticket/14199
------------------------------------------------------------------------------
  Ticket             | 14199
  Updated By         | Thomas Jarosch <thomas.jarosch at intra2net.com>
  Summary            | Decoding of base64 encoded Kolab (.xml) objects is
                     | broken
  Queue              | Kolab
  Type               | Bug
  State              | Unconfirmed
  Priority           | 1. Low
  Milestone          |
  Patch              | 1
  Owners             | Thomas Jarosch
------------------------------------------------------------------------------


Thomas Jarosch <thomas.jarosch at intra2net.com> (2015-12-17 10:36) wrote:

> Btw. the issue is 100% reproducible with Horde caching disabled.
>
> With caching enabled, things behave rather unpredictable.
>
> For tasks in Nag, the situation was this:
>
>   o caching enabled
>   o create tasks with Umlauts (works)
>   o tasks are shown in Nag and Kronolith
>
> Then...
>
>   o run horde-clear-cache
>   o logout/login
>   o those tasks with special chars are gone now...

thanks for the reproduction steps. I can take a look at this in the  
middle / end of January.
(currently busy with a time critical project that needs to be finished  
before the end of the year)

So basically having a contact picture + umlaut + disabled caching  
should trigger the problem in turba.
Hmm, really odd.