Last modified: 2011-03-13 18:06:02 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.
Oversighting images sounds good to me.
(In reply to comment #1) > Oversighting images sounds good to me. I thought oversighting was just for articles?
Please don't post "yeah, +1" style comments on bug reports. Thank you.
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.
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 :) )
*** Bug 12552 has been marked as a duplicate of this bug. ***
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.
*** Bug 12646 has been marked as a duplicate of this bug. ***
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)
Done in 32278 - r32685.
Actually, it isn't fixed. Please, check bug component before closing bug and don't confuse oversight extension with rev_deleted.
This extension was only a temporary hack until the new deletion system was made.
This is done with revisiondelete. It should not be done in the temporary Oversight extension. Request to enable it would be a separate bug.
(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.
