Last modified: 2011-01-25 00:46:25 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 15389 - Special:AllMessages is too large
Special:AllMessages is too large
Status: RESOLVED DUPLICATE of bug 16497
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2008-08-31 09:44 UTC by folengo
Modified: 2011-01-25 00:46 UTC (History)
3 users (show)

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


Description folengo 2008-08-31 09:44:49 UTC
Special:Allmessages is too heavy to use on my computer. Trying to read it with the monobook skin almost freezes my computer, and I have to shut the window using Ctrl+Alt+Del.

Even reading it offline, after downloading is critical. 

The size of is presently 2,153 Kbytes. I am afraid this is too much.

My suggestion : divide it into pages. For example into four smaller parts :

1) from Mediawiki:A... to Mediawiki:E...
2) from Mediawiki:F... to Mediawiki:J...
3) from Mediawiki:K... to Mediawiki:O...
4) from Mediawiki:P... to Mediawiki:Z...
Comment 1 MZMcBride 2008-10-06 23:34:06 UTC
Indeed, pagination and a better search function are what's needed. And some kind of decent view for big messages.
Comment 2 Chad H. 2009-03-05 13:44:50 UTC

*** This bug has been marked as a duplicate of bug 16497 ***

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