[Tickets #7631] first saved entry fails

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/7631
------------------------------------------------------------------------------
  Ticket             | 7631
  Created By         | jas at cse.yorku.ca
  Summary            | first saved entry fails
  Queue              | Ingo
  Version            | 1.2.1
  Type               | Bug
  State              | Unconfirmed
  Priority           | 3. High
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


jas at cse.yorku.ca (2008-11-04 14:09) wrote:

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.