Last modified: 2013-03-26 11:25:20 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 13297 - Search result page numbers should be rounded to nearest integer
Search result page numbers should be rounded to nearest integer
Product: Wikimedia
Classification: Unclassified
lucene-search-2 (Other open bugs)
All All
: Lowest enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2008-03-09 01:54 UTC by Gurch
Modified: 2013-03-26 11:25 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description Gurch 2008-03-09 01:54:20 UTC
Any request for search results where the "offset" isn't a multiple of the "limit" returns fractional page numbers, for example

While technically correct this looks a bit odd, and I think it would be better to just round each number to the nearest integer before displaying it.
Comment 1 Brion Vibber 2008-03-11 21:43:49 UTC
This issue seems specific to the LuceneSearch extension's front-end, which is on the way out.
Comment 2 Brion Vibber 2008-03-19 00:11:14 UTC
WONTFIXing this as we're about to dump LuceneSearch front-end for the built-in one which doesn't suffer from the problem.
Comment 3 Andre Klapper 2013-03-26 11:25:20 UTC
[Merging "MediaWiki extensions/Lucene Search" into "Wikimedia/lucene-search2", see bug 46542. You can filter bugmail for: search-component-merge-20130326 ]

Note You need to log in before you can comment on or make changes to this bug.