Last modified: 2007-05-11 01:50:54 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 9808 - User contributions limit is always 50 by default, rather than what was set in preferences
User contributions limit is always 50 by default, rather than what was set in...
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
All All
: Normal minor (vote)
: ---
Assigned To: Nobody - You can work on this!
: 9744 (view as bug list)
Depends on:
  Show dependency treegraph
Reported: 2007-05-06 10:45 UTC by ais523
Modified: 2007-05-11 01:50 UTC (History)
1 user (show)

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


Description ais523 2007-05-06 10:45:43 UTC
It used to be that the number of contributions displayed on [[Special:Contributions]] 
by default was determined by preferences (like [[Special:Recentchanges]] is), but 
recently the default number is always 50. This change appears to have been introduced 
with r21664 (then removed in r21666 and reinstated in r21667), where a hardcoded 50 
is now used. It's quite possible that the former behaviour was accidental, but it was 
quite useful; is there a good reason for a hardcoded limit now, or can that specific 
part of the revision be reverted (it was only a small part of a large change)?
Comment 1 Brion Vibber 2007-05-08 21:08:19 UTC
Fixed on trunk in r22010, r22011 on REL1_10
Comment 2 Brion Vibber 2007-05-11 01:50:54 UTC
*** Bug 9744 has been marked as a duplicate of this bug. ***

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