Hello Alec, and sorry for the longer delay:
On 20.04.2012 15:36, A.L.E.C wrote:
On 20.04.2012 15:32, Achim wrote:
[1] Which in itself is perhaps a side effect from RC trying to generate N: by assuming a "2-value FN:"?
Yes. All of this because you have both surname and firstname in required_fields definition. Here one doesn't exist, that's why the contact isn't imported. The logic is in rcube_ldap::validate() method.
I'm not sure we should do exception for import.
As Andreas pointed out in his follow-up message:
On 20/04/2012 17:11, Andreas Dick wrote:
InetOrgPerson requires sn and cn... if they are reqired fields, RC is trying to suggest them somehow and it works... but this is not perfect yet :-)
Is there any chance to cover at least the most probable fringe cases, such as the one mentioned above (only first or only last name, not both)?
I would believe that it is more convenient to be able to import 100 contacts out of which some have autogenerated (i.e. perhaps "wrong") information added, which can be easily detected and corrected by even an untrained user. The alternative (a user having to find out and manually update those contact information that have *not* been imported from a single, not human-friendly VCF file) seems a lot less desirable.
Would adding some "autogenerator code" be possible for rcube_ldap::validate()?
Thanks for your consideration, Achim