Last modified: 2011-03-13 18:05:14 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 T9334, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 7334 - Allow delete of unviewed versions
Allow delete of unviewed versions
Product: MediaWiki
Classification: Unclassified
History/Diffs (Other open bugs)
All All
: Lowest enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2006-09-15 07:11 UTC by Dave Yost
Modified: 2011-03-13 18:05 UTC (History)
0 users

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


Description Dave Yost 2006-09-15 07:11:12 UTC
If user x saved both versions n and n+1 of a page, and if no other users have viewed version n, then the history page 
that user x sees should have a delete link next to version n.

This feature would enable clutter reduction, saving user brainpower and saving disk space, and it would enable 
embarrassment reduction.
Comment 1 Brion Vibber 2006-09-15 07:12:12 UTC
There's basically no such thing as an 'unviewed' revision; it will have been shipped out to bots, mirrors, backups, etc already even 
in the unlikely case that no human looked at it yet.
Comment 2 Dave Yost 2006-09-15 08:38:23 UTC
OK, count those events you mention as views by another user, or ignore them with an option variable.

Wikipedia and some other mega-installations are of course the most important installations of MediaWiki, but the other 97.3% of 
installations have no mirroring or replication.  Bots are a nonissue because who cares if a bot picks up a version that goes stale before 
someone gets to it via a search engine.

Also, I would like to strengthen this request: a view via the history page should not count.

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