Last modified: 2013-04-11 15:24:13 UTC
Created attachment 11441 [details] Source: https://commons.wikimedia.org/w/index.php?title=File:%C3%89lisabeth_Louise_Vig%C3%A9e_Le_Brun_%28French_-_The_Vicomtesse_de_Vaudreuil_-_Google_Art_Project.jpg&redirect=no&uselang=en Will attach screenshots showing the issue. Both files were moved and I took a screenshot of the redirect page left behind (&redirect=no) One page only displays like a usual redirect [correct behaviour]; the second page however shows a redirect and claims there wouldn't be such a file and that you can upload it [wrong behaviour] like it is usually done when a file description page exists but no file. So the second page seems "not to know" that it is a redirect. Note that also their GlobalUsage page ([[Special:GlobalUsage]]) differs (no screenshots attached): * First file with thumb: https://commons.wikimedia.org/wiki/Special:GlobalUsage/%C3%89lisabeth_Louise_Vig%C3%A9e_Le_Brun_%28French_-_The_Vicomtesse_de_Vaudreuil_-_Google_Art_Project.jpg ) * Second file without thumb: https://commons.wikimedia.org/wiki/Special:GlobalUsage/Zoltan_Bathroy.jpg For bug-searching, here is the content of the "wrong behaviour redirect": No file by this name exists, but you can upload it. If a file used to exist, try to purge this page's cache #REDIRECTFile:Zoltan Bathory.jpg File usage on Commons There are no pages that link to this file.
Created attachment 11442 [details] "wrong rendering": Source: https://commons.wikimedia.org/w/index.php?title=File:Zoltan_Bathroy.jpg&redirect=no&uselang=en
Just for the record, I am logged-in there and I can't tell you whether other wikis are also affected. Purging the redirect pages does not help.
While that sounds really odd. --- When I visit the links, I get the expected behavior for both (Also global usage looks the same for both files for me). Is this something that still appears for you, or was it a temporary/intermittent issue?
(In reply to comment #3) Ok, had a look at some recently moved files and it seems like it "fixes itself" within 24h. Just go to https://commons.wikimedia.org/w/index.php?title=Special%3ALog&type=move&user=&page=&year=&month=-1&tagfilter= select a recently moved file (source position of course) and you will likely get the "wrong rendering". If you then go 24h or more back, you'll see that they render correctly. Global usage display seems to be strongly related to the (in-)correct rendering of the redirect. So I am not sure whether this is expected behaviour or some bug that could cause other bugs as well or whether it is a single isolated issue.
Looks like this is caused by bug 42616? Close as duplicate? https://commons.wikimedia.org/w/index.php?title=File:Uk_orkney.svg&action=history That redirect showed the symptoms described here, and it had two newlines after the redirect. When I deleted one of the newlines, it worked.
Confirmed on File:Flag_of_Orkney.png and File:Flag_of_Orkney.svg, too.
(In reply to comment #5) >When I deleted one of the newlines, it worked. But who deleted the two new lines at https://commons.wikimedia.org/w/index.php?title=File:%C3%89lisabeth_Louise_Vig%C3%A9e_Le_Brun_%28French_-_The_Vicomtesse_de_Vaudreuil_-_Google_Art_Project.jpg&redirect=no&uselang=en ? MediaWiki itself? Why? When? BTW, one can add arbitrary content or changing nothing and re-save and it gets fixed: https://commons.wikimedia.org/w/index.php?title=File%3ASLicon_VP2_L1.png&action=historysubmit&diff=84245913&oldid=84230075
(In reply to comment #5) > Looks like this is caused by bug 42616? Close as duplicate? > > https://commons.wikimedia.org/w/index.php?title=File:Uk_orkney. > svg&action=history > > That redirect showed the symptoms described here, and it had two newlines > after > the redirect. When I deleted one of the newlines, it worked. I think its less likely that the two new lines are causing the issue, and more likely the edit caused some sort of cache to be purged. (However it should be noted that a linksupdate via the api does not cause the issue to be fixed) My bet is something in memcache is not being updated when redirected. Thus the image page code is not detecting it is a redirect, and passing it off to Article to be rendered, which results in the mixed ui. After 24 hours the thing in memcache falls out of cache. [This is of course all conjecture].
(In reply to comment #8) > My bet is something in memcache is not being updated when redirected. There have been quite some architecture changes lately (move to new datacenter in January etc), so retesting is welcome.