Fri, 10 Apr 2026 09:35:34 +0000 https://bugs.horde.org/ticket/7631 first saved entry fails I am having a weird problem in Ingo where, for example, user logs in and enables "Forward", logs out and back in and the status is still disabled. I can confirm the following: If I login, and forwarding is "disabled" (ie. an X showing on the "Filters screen), I do indeed see in the database a PHP serialized component including: ... "disable";b:1; So, it really is disabled. if I click on the X, it turns to a checkmark, but when I check in the database, I still see: ... "disable";b:1; I then click on the checkmark, and it turns to an X. Of course the database remains: ... "disable";b:1; Now, if I click on the X, it turns to a checkmark, and the database entry is updated: ... "disable";b:0; Now, I can flip back and forth, and the database entry gets updated properly. Why is the first update "failing"? This happens on everything in Ingo. I am using Horde 3.1.3. Tue, 04 Nov 2008 19:09:15 +0000 https://bugs.horde.org/ticket/7631#t50267 When I changed the backend from horde_prefs to SQL, and imported all my data, the problem went away. Nonetheless, I guess this is still a bug. Tue, 04 Nov 2008 21:27:22 +0000 https://bugs.horde.org/ticket/7631#t50273 Duplicate of bugs #5901 and #4370. Sun, 09 Nov 2008 09:50:33 +0000 https://bugs.horde.org/ticket/7631#t50579