|
|
|
[
Permlink
| « Hide
]
Andrew Seymour - 06/20/08 09:49 AM
Personally, i don't think this is a Spark issue seen as Spark is just parsing the vcard that is sent, all vcards from jabber should essentially contain the same properties, if Openfire isn't sending the nickname or other things because of LDAP then ideally it needs to be fixed there.
Andrew, Todd and I were talking about this and — vcards for new accounts are empty. Psi does (I think this is a good thing) a thing where if it gets back no vcard for the user logging in it pops up a "you should fill in your profile!" dialog automatically. I've always liked this. I don't know if you think it's a wretched idea though. ;D Soemthing to consider though.
IMO Spark ought to do "has nickname? use that no? try first and last name no? use jid (or maybe first part of jid) What is the symtom Todd? what do the entities in the roster look like without this nickname field set? I assume not "blank" =) Well. When users are registered by admin, he is specifying Name field in Create User form. And Spark and other clients are using that field to display in roster, so no vCard is needed at all. So i dont wish such popup to be added, as vCards Nickname field is still empty in that case.
The issue comes into play when trying to manually add a user to a roster. If there is no nickname field for spark to use it defaults the username as it was entered during account creation. This could be anything tg2471 or something like that. Shared groups on the other hand default to the Name data as entered when creating an account. This is the same for LDAP which uses <nameField> which can be set to what ever the admin likes (<nameField>displayName</nameField>). In short the add contact to roster needs to change to auto reference some field that is present in every account created on the server, like the name field. Right now if an LDAP openfire server has the vCard field for nickname configured (<NICKNAME>{displayName}</NICKNAME> ) that info auto-populates to the new contact dialog box when the user account is entered. We need a similar functionality for those accounts that do not have data there. It is partially there in that it auto completes with the username.
Ok, i have just tried that. Actually it's adding it with Username (bare JID), not a Nickname. I can agree that Spark could be changed to add user from search or button using Name field instead. Or maybe it should do some logic as Daniel described (Name, Nickname, First Name, Username, etc.)
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||