6.0.0-beta6
▾
Tasks
New Task
Search
Photos
Wiki
▾
Tickets
New Ticket
Search
dev.horde.org
Toggle Alerts Log
Help
4/10/26
H
istory
A
ttachments
C
omment
W
atch
Download
Comment on [#7631] first saved entry fails
*
Your Email Address
*
Spam protection
Enter the letters below:
. ..___. .__ .___. |__|[__ | [__) _/ | || |___| \./__.
Comment
> 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. > > > > > >
Attachment
Watch this ticket
N
ew Ticket
M
y Tickets
S
earch
Q
uery Builder
R
eports
Saved Queries
Open Bugs
Bugs waiting for Feedback
Open Bugs in Releases
Open Enhancements
Enhancements waiting for Feedback
Bugs with Patches
Enhancements with Patches
Release Showstoppers
Stalled Tickets
New Tickets
Horde 5 Showstoppers