Last modified: 2014-03-09 18:06:13 UTC
I have stumbled upon a serious problem: When using this script <http://commons.wikimedia.org/wiki/User:Maxim/nuke.js> , (mass-delete tool), sometimes it only zaps the file itself. However, the image description page, with the history, still remains. This action of deleting the file alone is NOT logged. This creates a potential for abuse, as an admin can potentially delete an image file for malicious means and there would be no way to catch the vandal.
Is it returning "Internal error" messages?
(In reply to comment #1) > Is it returning "Internal error" messages? > I would have no way of knowing, as the script works like this in a nutshell: It first lists all the images in the category, with a choice to delete or not. After you confirm what you wish to delete and what you don't wish to delete, it relists all the image names, it loads data, then it deletes and only says that it did, in fact delete the image.
*** This bug has been marked as a duplicate of bug 12129 ***
Reopening this; this is a bit separate from bug 12129 as image page deletion has the additional step of doing two *separate* sub-items (delete the file, delete the page) and then logging. Per the original note, the breakage here was between those two, rather than necessarily between the second item and the log.
(In reply to comment #4) > Reopening this; this is a bit separate from bug 12129 as image page deletion > has the additional step of doing two *separate* sub-items (delete the file, > delete the page) and then logging. Per the original note, the breakage here was > between those two, rather than necessarily between the second item and the log. > Well the description deletion issue is fixed now, logging still a problem sometimes.
(In reply to comment #5) > (In reply to comment #4) > > Reopening this; this is a bit separate from bug 12129 as image page deletion > > has the additional step of doing two *separate* sub-items (delete the file, > > delete the page) and then logging. Per the original note, the breakage here was > > between those two, rather than necessarily between the second item and the log. > > > > Well the description deletion issue is fixed now, logging still a problem > sometimes. > I don't think it is fixed. I'll keep my eyes peeled for a more recent case, but I'm pretty sure the described scenario still occurs.
Maxim / Mike.lifeguard: Is this still a problem?
No answer from reporter to comment 7 and comment 8 and no indication that this still happens. => Unfortunately closing this report as no further information has been provided. Maxim: Please feel free to reopen this report if you can provide the information asked for and if this still happens. Thanks!
