Tickets :: [#4341] turba browse function

6.0.0-beta1

10/18/25

Summary	turba browse function
Queue	Turba
Queue Version	HEAD
Type	Bug
State	Resolved
Priority	2. Medium
Owners
Requester	ehymel (at) e-medico (dot) com
Created	08/26/2006 (6993 days ago)
Due
Updated	10/18/2006 (6940 days ago)
Assigned	08/28/2006 (6991 days ago)
Resolved	10/18/2006 (6940 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

10/18/2006 09:40:02 PM	Jan Schneider	Comment #8 State ⇒ Resolved	Reply to this comment
Eh, no.

10/18/2006 09:22:28 PM	Jan Schneider	Comment #7	Reply to this comment
Yes.

10/18/2006 06:20:40 PM	Chuck Hagenbuch	Comment #6	Reply to this comment
Jan - do you still see this?

08/28/2006 09:31:43 PM	Jan Schneider	Comment #5	Reply to this comment
It's not that easy. My default address book (localsql) has more than 20 contacts and is showing fine. But for all the other address books I can reproduce this behaviour now.

08/28/2006 09:17:49 PM	Chuck Hagenbuch	Comment #4	Reply to this comment
Okay, so for both Jan and the original reporter, do problems appear after the perpage threshhold is passed, but not before?

08/28/2006 02:40:39 PM	Matt Selsky	Comment #3	Reply to this comment
I'm seeing this here as well. SQL backend for addressbook book and I have 22 contacts. Everything was fine when I only had 18 contacts. perpage is set at the default of 20.

08/28/2006 11:21:05 AM	Jan Schneider	Comment #2 State ⇒ Feedback	Reply to this comment
Works perfectly here. You need to provide much more details about your configuration and preferences.

08/26/2006 05:44:53 PM	ehymel (at) e-medico (dot) com	Comment #1 Priority ⇒ 2. Medium State ⇒ Unconfirmed Queue ⇒ Turba Summary ⇒ turba browse function Type ⇒ Bug	Reply to this comment
Somewhere between ListView.php versions 1.56 and 1.59 the Browse function in turba got broken. Formerly clicking Browse showed the alphabet across the top of the page, defaulting to the letter 'A' for contacts starting with that letter. Now Browse simply shows "No matching contacts". Reverting from version 1.59 to 1.56 of ListView fixes this. I have not tried any versions in between. Thanks for all your hard work. Ernie Hymel