[Tickets #2411] NEW: Identify information not being saved

[bugs@bugs.horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/?id=2411
-----------------------------------------------------------------------
 Ticket             | 2411
 Created By         | kevin_myer at iu13.org
 Summary            | Identify information not being saved
 Queue              | Horde Framework Packages
 Version            | HEAD
 State              | Unconfirmed
 Priority           | 1. Low
 Type               | Bug
 Owners             | 
-----------------------------------------------------------------------


kevin_myer at iu13.org (2005-08-08 08:57) wrote:

A number of people have reported having trouble with identity preferences
not being saved.  In my case, I have defined hooks to lookup values for
from_addr and fullname, using some LDAP searches.  These preferences, and
'default_identity' are locked.  The lookups are occuring, but no values are
ever being saved.  As a work around, I unlocked fullnam and from_addr and
values are saved.

Amy Rich <amy.rich at tufts.edu> reports that users are unable to save any
information within their Default Identity, unless they specifically create
an identity.  None of her preference values are locked.

Jeffrey Steinbrecher <jsteinbrecher at gmail.com> reports that he has been
unable to create a Default identity and save preferences.

Somewhat anecdotally, I've never had this problem myself (nor have a few
other early adopters here).  However, before we locked preferences, we all
had setup multiple identities, which may explain why things always worked
for us, even after we locked preferences, but failed for new users.

So in summary, not having any identities saved for a user appears to result
in that user not being able to save preferences to the Default Identity.