Mehmet Giritli | 29 Mar 2012 15:14
Picon

No alphabetical categorisation for certain ldap backends

Hi list,

I have a number of ldap sources configured and currently working with a
minor problem. Some of my addressbooks are missing the alphabetical
listing feature that the other addressbooks have when you select them.
I'm talking about the bar at top of the listing which is like "(All) A B
C ....". When I select such an addressbook I don't see the bar at all
and I get a complete listing of the contents of the addressbook. What
might be the factors in the ldap configuration that is causing this?

I have two addressbooks from a ldap server pointing at different roots
and while one of them exhibit the problem, the other one doesn't.

When I change the root of the problematic addressbook to point the same
root as the working one, I get the alphabet bar. This must be something
with the ldap configuration, but I have no clues where to start...

Any tips would be highly appreciated.

Thanks.

--

-- 
turba mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: turba-unsubscribe <at> lists.horde.org

Jan Schneider | 29 Mar 2012 15:40
Favicon
Gravatar

Re: No alphabetical categorisation for certain ldap backends


Zitat von Mehmet Giritli <mgiritli <at> giritli.eu>:

> Hi list,
>
>
> I have a number of ldap sources configured and currently working with a
> minor problem. Some of my addressbooks are missing the alphabetical
> listing feature that the other addressbooks have when you select them.
> I'm talking about the bar at top of the listing which is like "(All) A B
> C ....". When I select such an addressbook I don't see the bar at all
> and I get a complete listing of the contents of the addressbook. What
> might be the factors in the ldap configuration that is causing this?

The size of the address book.

> I have two addressbooks from a ldap server pointing at different roots
> and while one of them exhibit the problem, the other one doesn't.
>
> When I change the root of the problematic addressbook to point the same
> root as the working one, I get the alphabet bar. This must be something
> with the ldap configuration, but I have no clues where to start...
>
> Any tips would be highly appreciated.
>
> Thanks.
>
> --
> turba mailing list
> Frequently Asked Questions: http://wiki.horde.org/FAQ
(Continue reading)

Mehmet Giritli | 30 Mar 2012 17:20
Picon

Re: No alphabetical categorisation for certain ldap backends

On Thu, 2012-03-29 at 15:40 +0200, Jan Schneider wrote:
> Zitat von Mehmet Giritli <mgiritli <at> giritli.eu>:
> 
> > Hi list,
> >
> >
> > I have a number of ldap sources configured and currently working with a
> > minor problem. Some of my addressbooks are missing the alphabetical
> > listing feature that the other addressbooks have when you select them.
> > I'm talking about the bar at top of the listing which is like "(All) A B
> > C ....". When I select such an addressbook I don't see the bar at all
> > and I get a complete listing of the contents of the addressbook. What
> > might be the factors in the ldap configuration that is causing this?
> 
> The size of the address book.

The address book which is working is the parent of the one which is not
working in the ldap hierarchy. Thus, size can not possibly be the
problem. In other words, I can see all the contacts from the address
book which is not working inside the one which is working and there are
some more contacts which only belong to the address book which is
working. The one which is working is strictly bigger that the one which
is not. I hope I didn't make it more complicated than it sounds...

Anyway, any other tips? There must be something else which can possibly
cause the disappearance of the alphabet bar...

By the way, could this log entry be related?

WARN: HORDE [turba] PHP ERROR: htmlspecialchars() expects parameter 1 to
(Continue reading)

Jan Schneider | 30 Mar 2012 17:47
Favicon
Gravatar

Re: No alphabetical categorisation for certain ldap backends


Zitat von Mehmet Giritli <mgiritli <at> giritli.eu>:

> On Thu, 2012-03-29 at 15:40 +0200, Jan Schneider wrote:
>> Zitat von Mehmet Giritli <mgiritli <at> giritli.eu>:
>>
>> > Hi list,
>> >
>> >
>> > I have a number of ldap sources configured and currently working with a
>> > minor problem. Some of my addressbooks are missing the alphabetical
>> > listing feature that the other addressbooks have when you select them.
>> > I'm talking about the bar at top of the listing which is like "(All) A B
>> > C ....". When I select such an addressbook I don't see the bar at all
>> > and I get a complete listing of the contents of the addressbook. What
>> > might be the factors in the ldap configuration that is causing this?
>>
>> The size of the address book.
>
> The address book which is working is the parent of the one which is not
> working in the ldap hierarchy. Thus, size can not possibly be the
> problem. In other words, I can see all the contacts from the address
> book which is not working inside the one which is working and there are
> some more contacts which only belong to the address book which is
> working. The one which is working is strictly bigger that the one which
> is not. I hope I didn't make it more complicated than it sounds...

You did. :) I lost you completely. Can you provide some examples instead?

> Anyway, any other tips? There must be something else which can possibly
(Continue reading)

Mehmet Giritli | 30 Mar 2012 18:08
Picon

Re: No alphabetical categorisation for certain ldap backends

On Fri, 2012-03-30 at 17:47 +0200, Jan Schneider wrote:
> Zitat von Mehmet Giritli <mgiritli <at> giritli.eu>:
> 
> > On Thu, 2012-03-29 at 15:40 +0200, Jan Schneider wrote:
> >> Zitat von Mehmet Giritli <mgiritli <at> giritli.eu>:
> >>
> >> > Hi list,
> >> >
> >> >
> >> > I have a number of ldap sources configured and currently working with a
> >> > minor problem. Some of my addressbooks are missing the alphabetical
> >> > listing feature that the other addressbooks have when you select them.
> >> > I'm talking about the bar at top of the listing which is like "(All) A B
> >> > C ....". When I select such an addressbook I don't see the bar at all
> >> > and I get a complete listing of the contents of the addressbook. What
> >> > might be the factors in the ldap configuration that is causing this?
> >>
> >> The size of the address book.
> >
> > The address book which is working is the parent of the one which is not
> > working in the ldap hierarchy. Thus, size can not possibly be the
> > problem. In other words, I can see all the contacts from the address
> > book which is not working inside the one which is working and there are
> > some more contacts which only belong to the address book which is
> > working. The one which is working is strictly bigger that the one which
> > is not. I hope I didn't make it more complicated than it sounds...
> 
> You did. :) I lost you completely. Can you provide some examples instead?

Okay. I have two address books, lets say A and B. They are pointing to
(Continue reading)

Jan Schneider | 30 Mar 2012 18:38
Favicon
Gravatar

Re: No alphabetical categorisation for certain ldap backends


Zitat von Mehmet Giritli <mgiritli <at> giritli.eu>:

> On Fri, 2012-03-30 at 17:47 +0200, Jan Schneider wrote:
>> Zitat von Mehmet Giritli <mgiritli <at> giritli.eu>:
>>
>> > On Thu, 2012-03-29 at 15:40 +0200, Jan Schneider wrote:
>> >> Zitat von Mehmet Giritli <mgiritli <at> giritli.eu>:
>> >>
>> >> > Hi list,
>> >> >
>> >> >
>> >> > I have a number of ldap sources configured and currently working with a
>> >> > minor problem. Some of my addressbooks are missing the alphabetical
>> >> > listing feature that the other addressbooks have when you select them.
>> >> > I'm talking about the bar at top of the listing which is like  
>> "(All) A B
>> >> > C ....". When I select such an addressbook I don't see the bar at all
>> >> > and I get a complete listing of the contents of the addressbook. What
>> >> > might be the factors in the ldap configuration that is causing this?
>> >>
>> >> The size of the address book.
>> >
>> > The address book which is working is the parent of the one which is not
>> > working in the ldap hierarchy. Thus, size can not possibly be the
>> > problem. In other words, I can see all the contacts from the address
>> > book which is not working inside the one which is working and there are
>> > some more contacts which only belong to the address book which is
>> > working. The one which is working is strictly bigger that the one which
>> > is not. I hope I didn't make it more complicated than it sounds...
(Continue reading)

Mehmet Giritli | 30 Mar 2012 18:50
Picon

Re: No alphabetical categorisation for certain ldap backends

On Fri, 2012-03-30 at 18:38 +0200, Jan Schneider wrote:
> Zitat von Mehmet Giritli <mgiritli <at> giritli.eu>:
> 
> > On Fri, 2012-03-30 at 17:47 +0200, Jan Schneider wrote:
> >> Zitat von Mehmet Giritli <mgiritli <at> giritli.eu>:
> >>
> >> > On Thu, 2012-03-29 at 15:40 +0200, Jan Schneider wrote:
> >> >> Zitat von Mehmet Giritli <mgiritli <at> giritli.eu>:
> >> >>
> >> >> > Hi list,
> >> >> >
> >> >> >
> >> >> > I have a number of ldap sources configured and currently working with a
> >> >> > minor problem. Some of my addressbooks are missing the alphabetical
> >> >> > listing feature that the other addressbooks have when you select them.
> >> >> > I'm talking about the bar at top of the listing which is like  
> >> "(All) A B
> >> >> > C ....". When I select such an addressbook I don't see the bar at all
> >> >> > and I get a complete listing of the contents of the addressbook. What
> >> >> > might be the factors in the ldap configuration that is causing this?
> >> >>
> >> >> The size of the address book.
> >> >
> >> > The address book which is working is the parent of the one which is not
> >> > working in the ldap hierarchy. Thus, size can not possibly be the
> >> > problem. In other words, I can see all the contacts from the address
> >> > book which is not working inside the one which is working and there are
> >> > some more contacts which only belong to the address book which is
> >> > working. The one which is working is strictly bigger that the one which
> >> > is not. I hope I didn't make it more complicated than it sounds...
(Continue reading)


Gmane