6.0.0-beta1
7/5/25

[#7935] use of file name filters might result incorrect empty result page
Summary use of file name filters might result incorrect empty result page
Queue Gollem
Queue Version 1.1-RC1
Type Bug
State Resolved
Priority 1. Low
Owners jan (at) horde (dot) org
Requester leena.heino (at) uta (dot) fi
Created 02/02/2009 (5997 days ago)
Due
Updated 03/19/2009 (5952 days ago)
Assigned 02/03/2009 (5996 days ago)
Resolved 03/19/2009 (5952 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
03/19/2009 02:19:15 PM Jan Schneider Assigned to Jan Schneider
Taken from Horde DevelopersHorde Developers
State ⇒ Resolved
 
03/19/2009 02:18:22 PM CVS Commit Comment #2 Reply to this comment
02/03/2009 03:45:48 AM Chuck Hagenbuch Assigned to Horde DevelopersHorde Developers
State ⇒ Assigned
 
02/02/2009 03:43:03 PM leena (dot) heino (at) uta (dot) fi Comment #1
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ use of file name filters might result incorrect empty result page
Queue ⇒ Gollem
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
Reply to this comment
You can recreate a problem like this:

1. Open a directory that has so many files that the directory listing 
has to be split into different pages.

2. Go to last page eg. page 5

3. Set file name filter to show eg. files beginning with a.

4. The filter result page is opened to page 5. If the filter results 
page can be fit in only page then the user sees an empty results page 
number 5.



What user expected to happen:

Show the first page of filter results, not the page number that user 
happened to be browsing in the original directory listing.

Saved Queries