[horde] Cannot save preferences [they just disappear]

[Roman Kurdel]

On 3/23/12 1:38 PM, Adam Tauno Williams wrote:
> On Thu, 2012-03-22 at 15:02 -0600, Michael M Slusarz wrote:
>> Quoting Adam Tauno Williams<awilliam at whitemice.org>:
>>> Quoting Adam Tauno Williams<awilliam at whitemice.org>:
>>>> Horde 4.0.14
>>>> I'm attempting to put together an install of the latest Horde
>>>> packages.  Horde is "running" just fine.  Adminsitration says all
>>>> the databases are current.
>>>> But I cannot save preferences.  The "save" completes, I even see
>>>> the INSERTs performed in the log ...
>>>> INSERT INTO horde_prefs (pref_uid, pref_scope, pref_name, pref_value)
>>>> 	  VALUES('adam', 'horde', 'identities',
>>>> 	  E'\\x613a313a7b693a303b613a31373a7b733a31363a2264656661756c745f6964656
>>>> 	  e74697479223b693a303b733a393a2266726f6d5f61646472223b733a32313a2261646
>>>>   **BUT*** if I log out and then back in the preferences are lost;
>>>> or at least no loaded.
>>>> I found<http://bugs.horde.org/ticket/10919>  which i thought might
>>>> be related but performing a "ALTER DATABASE horde SET bytea_output
>>>> = 'escape';" didn't effect the issue.
>>>> I don't see any log messages indicated there are errors
>>>> *loading/reading* the preferences from the back-end [the same
>>>> PostgreSQL database Horde uses overall].
>>>> Any pointers would be appreciated.
>>> If I "select * from horde_prefs" in the "SQL Shell" provided under
>>> "Administration" I see a result of the pref_uid, pref_scope,
>>> pref_name, and pref_value.  But in the display all the pref_value
>>> values are empty/blank.  Does the shell not display BYTEA values or
>>> does this indicate that Horde is unable to parse the values of those
>>> columns?
>> Did you update/migrate the DB?  The field types from the prefs data
>> has changed.
> No, this is a new database.  I created the database with creatdb, owned
> by the Horde user, and Horde created the schema.
>
> sudo  -u postgres createdb -E utf-8 -O horde horde5
>
> The pref_value column is type bytea.  Is that incorrect?
>
I experienced same problem and it was because I had old pdo (as I was 
running it on debian squeeze with postgresql 9.1 from backports). I went 
back to postgres 8.4 as it was an issue to me but tested it also on 
debian wheezy and there it worked correctly even with 9.1 postgres

-- 
Roman Kurdel
IT Support
blueDRM s. r. o.