Last modified: 2014-04-30 11:03:53 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 3753 - Option to hide rows from Special:Contributions where the edit is the most recent to a page
Option to hide rows from Special:Contributions where the edit is the most rec...
Status: REOPENED
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
unspecified
All All
: Low enhancement with 5 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
: easy
: 13032 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-10-20 02:58 UTC by Richard Frantz Jr.
Modified: 2014-04-30 11:03 UTC (History)
8 users (show)

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


Attachments

Description Richard Frantz Jr. 2005-10-20 02:58:34 UTC
Request for option to suppress entries on special page: User Contributions where latest edit to 
article is by the user.  This is to mke it easier to skim for how people are improving edits I made.
Comment 1 Rick DeNatale 2006-01-13 17:22:58 UTC
I came across this bug preparatory to filing a new feature request for the
opposite, i.e. I'd like to be able to see only the contributions from a user
which ARE the latest edit of an article.

The motivating use case is:

1) I see an article which has been spammed or kiddie-edited.
2) I want to clean up other articles from the same "contributor" so I look at
their contributions e.g.
http://en.wikipedia.org/w/index.php?title=Special:Contributions&target=216.255.121.69
3) But now I need to look at each article's history to see not only if it's been
deface, but also if so it hasn't already been dealt with.
Comment 2 Rob Church 2007-04-02 06:53:24 UTC
I'm not convinced the feature described in comment 0 would be useful. I can see
the use for that of comment 1, however.
Comment 3 Alexandre Emsenhuber [IAlex] 2010-04-20 16:23:59 UTC

*** This bug has been marked as a duplicate of bug 13032 ***
Comment 4 Waldir 2011-02-08 18:08:09 UTC
Reopening and reversing the duplicate direction. See comment 2 on bug 13032 for the explanation.
Comment 5 Waldir 2011-02-08 18:08:16 UTC
*** Bug 13032 has been marked as a duplicate of this bug. ***
Comment 6 Waldir 2011-02-08 19:11:17 UTC
The complement to this bug is bug 4597, which requests the implementation of a filter to display only the top edits in special:contributions (useful to track "unreviewed" edits by a newbie or vandal). Since that functionality was implemented through a checkbox, I suggest this bug to be implemented as a conversion/expansion of that system into a radio button group ("hide top"/"hide old"/"show all").
Comment 7 K N 2011-07-22 19:25:27 UTC
(In reply to comment #2)
> I'm not convinced the feature described in comment 0 would be useful. I can see
> the use for that of comment 1, however.

Quite the contrary, I think it would prove very useful. As far as I can tell, it seems to be how many contributors actually proceed in WP: as they are working on a given page, they actively monitor if (and what) others have edited after one's own contributions... This "how dare they?!" attitude seems a big driving force!  To allow showing only those pages where the user is not the last contributor would really make this monitoring easier.  

To my opinion, as this "hide top edits" option would be useful for virtually all regular WP contributors, it would be even more widely used than the novel   option (r1.17) to "show only top edits" (which mainly addresses to rollbackers and the like described in comment #1).

As comment #6, I agree that a 3-alternative radio button could be one way to go. 
However, I think this option should be on the Special:Watchlist rather than on the Special:Contributions. For it is aimed at monitoring pages rather than users.

Please note that, to be really useful, the "hide top edits" option would need to also hide all earlier edits on those pages where the user is the last contributor (i.e. not only the last edits).

Cheers
Comment 8 Waldir 2011-07-22 21:24:56 UTC
(In reply to comment #7)
> I think this option should be on the Special:Watchlist rather than on the
> Special:Contributions. For it is aimed at monitoring pages rather than users.

I agree with almost everything you say, except the above. Personally, I use the Special:Contributions page as a temporary watchlist, for articles I edit and want to follow for a short period of time aftwewards, to see the reactions to my edits, but don't want to keep in my watchlist permanently. I believe many editors do the same thing, so until we have a way to include pages in our watchlist with an expiry date, I believe special:contributions is the best place to have this. Or even better, we have it on both pages :)
Comment 9 Cristian B. 2012-01-04 12:31:16 UTC
I suppose the similar hiding of "all *earlier* edits on those pages where the user *later contributed*, that is - not the last edits themselves" would be too much to ask for? :-)
Comment 10 Thor Malmjursson 2012-07-06 21:12:44 UTC
I'd back this too - I was about to file a feature request on this when I noticed it pop up in the possible duplicates.  I've tried this with the watchlist, but there are far more pages on my watchlist than I've actually edited - so the sensible thing imo would be to have pages which haven't been edited since you last worked on them, suppressed from view in Special:Contributions - it would be a big help.
Comment 11 PiRSquared17 2014-04-26 01:21:43 UTC
This is possible with API already, and should be easy (although I'm not sure how the UI would look with another checkbox)
Comment 12 PiRSquared17 2014-04-26 01:23:37 UTC
(In reply to PiRSquared17 from comment #11)
> This is possible with API already, and should be easy (although I'm not sure
> how the UI would look with another checkbox)

Actually I guess the API has something for bug 30068 if you want to be technical.
Comment 13 Cristian B. 2014-04-30 11:03:53 UTC
(In reply to PiRSquared17 from comment #11)
> This is possible with API already, and should be easy (although I'm not sure
> how the UI would look with another checkbox)

Would you please elaborate on that? (since not everyone is familiar with the API, and/or how to use it while contributing via the default interface.) I don't think crowding up the interface would be anyone's major concern... and in any case, you can have such "advanced" checkboxes hidden inside a collapsible area of the page, so that they would show up only for people who really want them.

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


Navigation
Links