Page MenuHomePhabricator

Partial move failure of 20110607_London_07.JPG
Open, MediumPublic

Description

Copying from https://commons.wikimedia.org/wiki/Commons:VP#File:AllSaints_store.2C_Westbourne_Grove.2C_London_W11.jpg_missing_thumbnails (perma-link: https://commons.wikimedia.org/w/index.php?title=Commons:Village_pump&oldid=101529355 )

[[commons:file:20110607_London_07.JPG]] was moved to [[commons:File:AllSaints store, Westbourne Grove, London W11.jpg]], however the image asset did not get moved. The page, and all database records, appear to have moved correctly, but the thumbs are missing. Since then somebody has uploaded a new version of the file (the oldimage record for the original file has the empty string as the value for oi_archive_name).

The original file can still be accessed at https://upload.wikimedia.org/wikipedia/commons/e/ed/20110607_London_07.JPG (mangling the url, https://upload.wikimedia.org/wikipedia/commons/e/ed/20110607_London_07.JPG?nocacheplz works too. However thumb urls don't work for the old filename).


Expected behaviour: File fully moves, or not at all. In case of error, file should fully stay at old location.


Version: 1.22.0
Severity: normal

Details

Reference
bz52660

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 22 2014, 2:01 AM
bzimport set Reference to bz52660.
bzimport added a subscriber: Unknown Object (MLST).

(In reply to comment #0)

The original file can still be accessed at
https://upload.wikimedia.org/wikipedia/commons/e/ed/20110607_London_07.JPG

Deleted this version by moving the file back and forth.

Is this a shell request to fix the erroneous database entry (per summary) or a report of the underlying bug in MediaWiki (per product field)?

(In reply to comment #2)

I think it is about the bug in the software. The software should be fixed to prevent this error in future. Also see:

( comment #0)

Expected behaviour: File fully moves, or not at all. In case of error, file
should fully stay at old location.

Note, this is not the first occurrence of this bug. I saw instances of files broken in this way (after moving) numerous times. However this is the first bug request addressing this issue, I think.