That's your problem; upgrading will fix it.

Currently I'm using Pear::DB v. 1.5.8 but after a quick look at 
pear.php.net I seen that Pear::DB is now at 1.6.5 so I will try with a 
more recent version when I will get more time to look at this 
(probably during the weekend).



Daniel Vandal

dvandal@infoteck.qc.ca

What version of PEAR::DB do you have?

Hi,



I don't know why, but the Prefs doesn't save in the MySQL database 
when I change them. I have this problem on 3 of my Horde 
installations, but what is strange is that some prefs are saved but 
the most aren't.



If I set the debug at PEAR_LOG_DEBUG to save everything, only a few 
SQL request are sent and that's only when the prefs are properly 
saved. I done a test by saving the prefs inside the Session and that's 
working, so I suspect a problem with the MySQL Prefs handler.



There is what I'm using on the 3 Horde installations :

Linux : Fedora Core 2

Apache : 2.0.50

PHP : 4.3.8

MySQL : Ver 12.21 Distrib 4.0.15, for pc-linux-gnu (i686)



2 Horde installation have using the same config and running on the 
same server using IMAP authentication (1 month old CVS copy), and 
another completly new using HEAD version (4 day old CVS copy) and both 
have the same problem.



I need to solve this problem because I'm currently writing a module 
for my work because all I need is to save a username and password in 
the prefs.



The request sent to save the prefs from my script is :

$prefs->setValue('sm_username', $sm_username);



If I do a var_dump($prefs), I see the prefs I asked set but as soon I 
refresh the page, the prefs are lost. But if I use the Session Prefs 
handler instead of MySQL, the prefs are properly stored. But we need 
to use SQL saved prefs.



Daniel Vandal

dvandal@infoteck.qc.ca