Last modified: 2014-03-09 18:06:13 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 13863 - Occasional error where a file gets deleted, but the image description doesn't, and the deletion is unlogged
Occasional error where a file gets deleted, but the image description doesn't...
Status: RESOLVED WORKSFORME
Product: MediaWiki
Classification: Unclassified
File management (Other open bugs)
unspecified
All All
: Low major with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
http://commons.wikimedia.org/wiki/Ima...
aklapper-moreinfo
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-04-27 20:15 UTC by Maxim
Modified: 2014-03-09 18:06 UTC (History)
7 users (show)

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


Attachments

Description Maxim 2008-04-27 20:15:50 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.
Comment 1 Aaron Schulz 2008-04-27 23:07:57 UTC
Is it returning "Internal error" messages?
Comment 2 Maxim 2008-04-27 23:17:55 UTC
(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. 
Comment 3 Aaron Schulz 2008-04-27 23:31:18 UTC

*** This bug has been marked as a duplicate of bug 12129 ***
Comment 4 Brion Vibber 2008-04-29 21:06:54 UTC
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.
Comment 5 Aaron Schulz 2008-04-29 22:48:47 UTC
(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.
Comment 6 Mike.lifeguard 2008-11-25 04:14:58 UTC
(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.
Comment 7 Andre Klapper 2013-02-11 10:11:06 UTC
Maxim / Mike.lifeguard: Is this still a problem?
Comment 8 Andre Klapper 2013-04-11 12:57:39 UTC
Maxim / Mike.lifeguard: Is this still a problem?
Comment 9 Andre Klapper 2014-02-12 17:18:59 UTC
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!

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


Navigation
Links