Last modified: 2011-03-13 18:05:43 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 808 - Allow watchlist to be sorted by number of edits
Allow watchlist to be sorted by number of edits
Status: RESOLVED WONTFIX
Product: MediaWiki
Classification: Unclassified
History/Diffs (Other open bugs)
unspecified
All All
: Lowest enhancement with 2 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on: 536
Blocks:
  Show dependency treegraph
 
Reported: 2004-10-30 18:17 UTC by Jens Müller
Modified: 2011-03-13 18:05 UTC (History)
1 user (show)

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


Attachments

Description Jens Müller 2004-10-30 18:17:03 UTC
Bug 536 asks to save the last visited revision (LVR) for pages in the watchlist.
Enotif (bug 454) (or related patches?) already utilise this to show in
Special:Watchlist that a page has been changed since last visited.

A further enhancement would be if the watchlist could somehow be sorted by the
number of edits since the last visit. For this to be possible without heavy
database load, the number of edits should be stored in the table that records
which user watches which pages. It would be set to 0 every time the user visits
the page, and an edit to the page would increase the number for all
corresponding records.
Comment 1 Brion Vibber 2004-11-04 01:48:51 UTC
Removing bogus double dependency
Comment 2 Aaron Schulz 2009-01-03 14:14:24 UTC
Closing due to performance issues with any implementation (unless someone has an epiphany here).

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


Navigation
Links