| Summary | Identify information not being saved |
| Queue | Horde Framework Packages |
| Queue Version | HEAD |
| Type | Bug |
| State | Resolved |
| Priority | 1. Low |
| Owners | Horde Developers (at) |
| Requester | kevin_myer (at) iu13 (dot) org |
| Created | 08/08/2005 (7395 days ago) |
| Due | |
| Updated | 11/03/2005 (7308 days ago) |
| Assigned | 09/13/2005 (7359 days ago) |
| Resolved | 11/03/2005 (7308 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
our site:
NAME: horde
VERSION: 3.0.5
NAME: imp
VERSION: 4.0.4
NAME: ingo
VERSION: 1.0.2
NAME: turba
VERSION: 2.0.4
State ⇒ Assigned
ldap then using hordeauth for imp/ingo/turba.
this ticket).
ldap then using hordeauth for imp/ingo/turba.
ldap then using hordeauth for imp/ingo/turba.
the system ask me about language and indecating "never login before"
the identity can't be saved as well.
nothing to do with the issue of this ticket.
the system ask me about language and indecating "never login before"
the identity can't be saved as well.
State ⇒ Feedback
fresh user fine.
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ Identify information not being saved
Queue ⇒ Horde Framework Packages
State ⇒ Unconfirmed
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@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@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.