Last modified: 2013-04-23 13:36:19 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T49314, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 47314 - Built-in pager class is handling non-unique column badly
Built-in pager class is handling non-unique column badly
Status: NEW
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
1.22.0
All All
: Low minor (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-04-17 12:11 UTC by Liangent
Modified: 2013-04-23 13:36 UTC (History)
1 user (show)

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


Attachments

Description Liangent 2013-04-17 12:11:11 UTC
An extreme case, af_enabled is either 0 or 1:

http://en.wikipedia.org/w/index.php?title=Special:AbuseFilter&sort=af_enabled&limit=50
Comment 1 Andre Klapper 2013-04-17 12:46:00 UTC
What exactly is the "bad handling" here? Could you elaborate (or attach a screenshot)?
Comment 2 Liangent 2013-04-17 13:13:03 UTC
(In reply to comment #1)
> What exactly is the "bad handling" here? Could you elaborate (or attach a
> screenshot)?

There're always two "pages" available: one for af_enabled=0 and another for af_enabled=1, regardless of how many entries are listed and how many are left.
Comment 3 Andre Klapper 2013-04-23 13:17:24 UTC
Is this an issue in MediaWiki core, and AbuseFilter just one example exposing the problem?
Comment 4 Liangent 2013-04-23 13:36:19 UTC
(In reply to comment #3)
> Is this an issue in MediaWiki core, and AbuseFilter just one example exposing
> the problem?

Correct.

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


Navigation
Links