Problems with Horde Interface after upgrade from 2.2.4 to 2.3.2

[Gunnar Wrobel]

Quoting "Andrew J. Kopciuch" <akopciuch at bddf.ca>:

> On June 7, 2011, Christoph Wickert wrote:
>> > All the settings that I am talking about were made through the Horde
>> > Options menu.  Specifically the ones mentioned are on Options->Global
>> > Options->Locale and Time.  I do not know where they are stored, but I
>> > had expected them to be carried over.
>> >
>> > Same with the Remote Calendars that I had subscribed to.  This was
>> > done with Calendars->Manage Calendars->Subscribe to Remotes Calendar.
>>
>> Frankly speaking I have no idea either, but I'll have Gunnar looking into
>> that.
>
>
> I thought the horde preferences were stored in LDAP?   After some  
> reading, and
> research it seems this changed sometime during the 2.2.x releases?

That depends. Old systems (< 2.2.1) used LDAP and in that case people  
were requested to stick to that as we had no preferences converter  
(see https://issues.kolab.org/issue3567). I recently wrote one for  
Horde 4 that is most likely also usable for Horde 3 on the Kolab but  
so far this has not been adopted by the Kolab side.

>
> https://issues.kolab.org/issue3567
>
> The LDAP storage is actually commented out in the  
> slapd.conf.template, and the
> webclient-kolab.php.template files.   So it is definitely _not_ in LDAP by
> default.
>
> The preferences should be stored on the filesystem then?  (I admit i do not
> know how the preference system works).   It looks like PHP session files?
> Located in : /kolab/var/kolab/www/client/tmp

The preferences are in /kolab/var/kolab/www/client/storage/*.prefs

>
> Does the upgrade of packages clear out that tmp directory?   That  
> would AFAICS
> wipe out all filesystem preferences stored in there.  If the default
> implementation for the web client prefs is to be stored in files, then should
> there not be a special directory to store them?  And not just in a tmp dir?
>

See above.

> If that is really the case, and I'm not misunderstanding something, then I
> think a bug should be filed on this.

There have been reports similar to yours that there is some problem  
with the preferences backend in 2.3.2 (possibly 2.3.*). I was not able  
to reproduce it on a plain 2.3.2 yet. But any input you have on the  
issue might help. Please add it to https://issues.kolab.org/issue4745


>
> --
>
> https://wiki.kolab.org/Horde_development#Prefs
>
> <snip>
> The Horde user preferences have been traditionally stored in the Kolab LDAP
> tree. This is still the recommended version and there exists a
> special "kolab" driver that implements this option. There are also other
> options available for storing the user preferences and you can choose between
> SQL db, file and IMAP based approaches if you don't want to use LDAP.
> </snip>
>
>
> Is this just a case of "out of date"?

No, this is not really out of date. The page in general may be but  
that section sounds fine. The tendency is to store preferences in IMAP  
at some point. Horde supports this since a long time already but I  
used a horde specific format for that and nothing the Kolab community  
has agreed upon on the kolab-format list. It looks as if that area  
might see some movement soon which would be very good.

Cheers,

Gunnar

>  I simply do not know enough in this
> area to definitively explain things.  I agree that Gunar is probably the
> expert on this.
>
>
>
> Andy

-- 
Core Developer
The Horde Project

e: wrobel at horde.org
t: +49 700 6245 0000
w: http://www.horde.org

pgp: 9703 43BE
tweets: http://twitter.com/pardus_de
blog: http://log.pardus.de