| Summary | first saved entry fails |
| Queue | Ingo |
| Queue Version | 1.2.1 |
| Type | Bug |
| State | Duplicate |
| Priority | 2. Medium |
| Owners | |
| Requester | jas (at) cse (dot) yorku (dot) ca |
| Created | 11/04/2008 (6091 days ago) |
| Due | |
| Updated | 11/09/2008 (6086 days ago) |
| Assigned | 11/09/2008 (6086 days ago) |
| Resolved | 11/09/2008 (6086 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
Taken from Jan Schneider
State ⇒ Duplicate
#5901and#4370.State ⇒ Assigned
Priority ⇒ 2. Medium
my data, the problem went away. Nonetheless, I guess this is still a
bug.
Priority ⇒ 3. High
Type ⇒ Bug
Summary ⇒ first saved entry fails
Queue ⇒ Ingo
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
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.