6.0.0-beta1
▾
Tasks
New Task
Search
Photos
Wiki
▾
Tickets
New Ticket
Search
dev.horde.org
Toggle Alerts Log
Help
10/22/25
H
istory
A
ttachments
C
omment
W
atch
Download
Comment on [#855] default first listing in the Browse
*
Your Email Address
*
Spam protection
Enter the letters below:
._.. ..__..__ . . | | || |[__)\ / _|_|__||__|| \/
Comment
>> We don't currently have a preference for which page to start with > >> (instead of all), and we do filtering client-side. We should fix both > >> of those, but patches would help immensely. > > > > Currently, the paging works based on the first character of the > displayed 'name' field - which is dependent on the user's name format > prefs. How would we go about filtering server-side without making > assumptions about the field structure on the backend? In other > words, we can check the prefs and see we are displaying "Lastname, > Firstname" but how can we search for this server side - not knowing > if there is a 'Lastname" field available, and if it is, what is it > called? I thought of putting a 'paging_search' entry into > $cfgSources, but that would force the name format pref to be the same > system wide, not per user... We could put it into the user prefs, > but would something like this be intuitive to the user? > > > > Thoughts?
Attachment
Watch this ticket
N
ew Ticket
M
y Tickets
S
earch
Q
uery Builder
R
eports
Saved Queries
Open Bugs
Bugs waiting for Feedback
Open Bugs in Releases
Open Enhancements
Enhancements waiting for Feedback
Bugs with Patches
Enhancements with Patches
Release Showstoppers
Stalled Tickets
New Tickets
Horde 5 Showstoppers