Page MenuHomePhabricator

Redirected image in Commons also redirected in local but in confusing manner
Open, LowPublic

Assigned To
Authored By
Jun 19 2013, 3:38 PM
Referenced Files
F11821: isthmus5.jpg
Nov 22 2014, 2:08 AM
F11820: isthmus4.jpg
Nov 22 2014, 2:07 AM
F11819: isthmus3.jpg
Nov 22 2014, 2:07 AM
F11817: isthmus1.jpg
Nov 22 2014, 2:07 AM
F11818: isthmus2.jpg
Nov 22 2014, 2:07 AM


For example

redirected to

without any explanation or edit history on en.wp

Turns out that it was redirected on Commons.

The issue with this is that (1) the content of the first page didn't showed up in the second page, (2) in the list of File Usage didn't list correctly the pages that used the image. Therefore there is no way to know which pages uses the image, such as [[List of isthmuses]] (

The WhatLinksHere special page also didn't recognize that the image was redirected on Commons, thus still regard them as separate files, but, since the first image can't be reached without hacking the URL, it was essentially "lost".

Redirected images on Commons should show an explanation in local just like in Commons, and the list of pages that used the image should be merged, as well as the backlinks in local

Version: 1.22.0
Severity: normal



Event Timeline

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

Created attachment 12582
the sample image


isthmus1.jpg (454×1 px, 170 KB)

Created attachment 12583
There's no explanation of the redirect done in Commons

Local editors could be left confused


isthmus2.jpg (445×574 px, 70 KB)

I think this is from InstantCommons, so moving to the MediaWiki product.

(In reply to comment #6)

I think this is from InstantCommons, so moving to the MediaWiki product.

InstantCommons isn't the right word (that usually only refers to ForeignAPIRepo, not ForeignDBViaLBRepo), but you're right to move component.

Anyhow, there are issues with cache invalidation when making file redirects from a foreign repo. They really should be explored and fixed. This possibly is another symptom of that, or it might also contain its own issues, not sure.

So this is possibly some combo of bug 18017, bug 22390 and possibly its own issue