Last modified: 2013-06-19 23:25:26 UTC
For example http://en.wikipedia.org/wiki/File:The_Spit_Bruny_Island.jpg redirected to http://en.wikipedia.org/wiki/File:The_Neck_Bruny_Island.jpg 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]] (http://en.wikipedia.org/w/index.php?title=List_of_isthmuses&oldid=559663455&action=edit) 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
Created attachment 12582 [details] the sample image
Created attachment 12583 [details] There's no explanation of the redirect done in Commons Local editors could be left confused
Created attachment 12584 [details] only 1 backlink Whereas actually there's more than 20, including POTD pages http://en.wikipedia.org/wiki/Wikipedia:Featured_picture_candidates/File:The_Spit_Bruny_Island.jpg http://en.wikipedia.org/wiki/Template:POTD/2009-11-24
Created attachment 12585 [details] http://en.wikipedia.org/wiki/Special:WhatLinksHere/File:The_Neck_Bruny_Island.jpg
Created attachment 12586 [details] http://en.wikipedia.org/wiki/Special:WhatLinksHere/File:The_Spit_Bruny_Island.jpg
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
