Warning possible too much info incoming:
What you describe is exactly the way the buttons are meant to work, and
exactly the way they work here for me :)
The buttons have to generate a new query because we can't simply filter
on existing search rules in the ldap case (since they may have been
On Fri, 2003-10-10 at 12:14, Chris Toshok wrote:
What you describe is exactly the way the buttons are meant to work, and
exactly the way they work here for me :)
I should point out that I meant the behavior you expect (as opposed to
what you're seeing) is the way they're meant to work.
:)
Ah. Well then, the problem is that we don't have any 'sn' attributes in
our LDAP server (which is OpenLDAP btw, and we don't have any
evolutionPerson stuff either).
I would expect that clicking on a letter would be precisely the same as
clicking search for Name begins with and then that letter.
hm, are you setting surname?
sn/surname is required of any objects that list person as an
objectclass.
The reason that it doesn't use the cn is that we want them to act like
the tabs on a real address book.. and that's based on how they're
sorted. which for evolution is either the fileAs or
