[Tickets #13865] Re: Application settings for "horde" application not updatable in IMAP/Kolab back-end

[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/13865
------------------------------------------------------------------------------
  Ticket           | 13865
  Aktualisiert Von | jmozdzen at nde.ag
  Zusammenfassung  | Application settings for "horde" application not
                   | updatable in IMAP/Kolab back-end
  Warteschlange    | Kolab
  Typ              | Bug
  Status           | Unconfirmed
  Priorität        | 3. High
  Milestone        |
  Patch            |
  Zuständige       |
------------------------------------------------------------------------------


jmozdzen at nde.ag (2015-02-17 17:28) hat geschrieben:

new detail:

while trying to locate the "load preferences" part of the source code,  
I logged off, then ran "horde-clear-cache" and then re-logged in.

Application:horde preferences were stored - and they were stored as  
quoted-printable, not as base64.

Unfortunately, these preferences were just "default" ones - at least  
not those that I had available until a few minutes ago.

And they received a new uuid - so the old prefs are still available as  
an IMAP message, but as an older one. And I see no way of re-estating  
the old preferences - deleting the cache will generate new ones.

Is it correct to assume that Horde preferences are read from the Horde  
cache (if available), rather than from the Kolab storage on every login?

My assumption given on the mailing list still holds true: This has  
somehow to do with Horde caching.