Last modified: 2011-03-13 18:06:02 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 T10196, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 8196 - Oversight of file histories including images
Oversight of file histories including images
Status: RESOLVED WONTFIX
Product: MediaWiki extensions
Classification: Unclassified
Oversight (Other open bugs)
unspecified
All All
: Lowest enhancement with 15 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
:
: 12552 12646 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-12-09 07:35 UTC by Dominic
Modified: 2011-03-13 18:06 UTC (History)
7 users (show)

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


Attachments

Description Dominic 2006-12-09 07:35:17 UTC
Currently only page revisions may be oversighted. However, non-public personally
identifiable or libelous images (and other media) can only be deleted. We
recently ran into this problem and could not have hidden a file without
developer help.
Comment 1 1ne 2006-12-09 22:37:39 UTC
Oversighting images sounds good to me.
Comment 2 1ne 2006-12-09 22:38:52 UTC
(In reply to comment #1)
> Oversighting images sounds good to me. I thought oversighting was just for articles?

Comment 3 Rob Church 2006-12-09 23:42:18 UTC
Please don't post "yeah, +1" style comments on bug reports. Thank you.
Comment 4 Aaron Schulz 2006-12-21 05:05:03 UTC
This may have to wait until live image storage is converted to FileStore format
like the archives. Otherwise the code would end up useless soon anyway.
Comment 5 Effeietsanders 2007-12-23 11:29:57 UTC
Is it already possible to fix this error? I have come across a few occasions now already where there was no possibility to remove the images, although that would have been preferrable (either because of the image itself, either because of a summary during the upload, which is visible very much in the file history. Also in the log's, but that's another story I assume :) )
Comment 6 spacebirdy 2008-01-08 18:42:13 UTC
*** Bug 12552 has been marked as a duplicate of this bug. ***
Comment 7 Brion Vibber 2008-01-09 01:28:21 UTC
Right now the image has to be deleted manually from the deleted image archive directory. This isn't very difficult, but it's a slight pain.

In theory it ought not to be too difficult to set up an alternate archive and an interface to move them over.
Comment 8 Brion Vibber 2008-01-15 21:17:53 UTC
*** Bug 12646 has been marked as a duplicate of this bug. ***
Comment 9 Larry Pieniazek 2008-01-16 19:49:28 UTC
Give that we have two dup bugs created, one by me (and  honestly, I searched for bugs that might be dups of it and did not find this one) I tried to add some keywords to hopefully forestall more dups. (That didn't work, so I changed the summary to add "images", a natural thing for non devs to search on ) I suspect that there will be increasing interest in this. bug 12646 has some UI suggestions that might be useful for the implementer to review (in a nutshell, please make the UI as much like text revision oversight as possible, and maybe use the same permissions group to control who can use it)
Comment 10 Aaron Schulz 2008-04-02 05:56:01 UTC
Done in 32278 - r32685.
Comment 11 Victor Vasiliev 2008-07-09 15:41:44 UTC
Actually, it isn't fixed. Please, check bug component before closing bug and don't confuse oversight extension with rev_deleted.
Comment 12 Aaron Schulz 2008-07-09 16:50:53 UTC
This extension was only a temporary hack until the new deletion system was made.
Comment 13 Aaron Schulz 2008-09-18 11:42:31 UTC
This is done with revisiondelete. It should not be done in the temporary Oversight extension. Request to enable it would be a separate bug.
Comment 14 Mike.lifeguard 2008-09-18 15:29:31 UTC
(In reply to comment #13)
> This is done with revisiondelete. It should not be done in the temporary
> Oversight extension. Request to enable it would be a separate bug.
> 

That would be bug 15029.

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


Navigation
Links