Last modified: 2009-04-10 14:19:27 UTC
Hi, I realize this isn't the greatest of bug reports, but I'll describe what I know, and hopefully you can make something of it. (My apologies if you can't.) I've visited http://en.wikipedia.org/wiki/Arata_Kochi in the past, and it's been fine. (Most recently, about a month ago.) Then I visited it the other day, and got the boilerplate "Wikipedia does not have an article with this exact name" message - but the "article" tab-style link at the top (I'm using the Monobook skin) was blue, meaning that some part of the software knew the article did exist (contrast, say, http://en.wikipedia.org/wiki/Horrid_typo, where the "article" tab-style link is red). Further, I could edit the page (and the edit box contained its current text) and navigate its history, which was intact. The problem got resolved for that specific article by purging the cache (which is why I've marked this bug a minor one), but it's my understanding that this isn't the normal purpose of the cache. The cache previously held this page, and it's my understanding that while the cache can be out-of-date, it should never be wrong in any other way. (Incidentally, I brought this up on the Village Pump, and other people mentioned other articles that have had this problem.) I hope that's even remotely helpful to you. :-/ Sincerely, Ran Ari-Gur (en:User:Ruakh on Wikipedia and Wiktionary)
1) Were you logged in at the time you saw the incorrect page display? 2) Has this happened on pages *after* they've been edited in the last two days?
1) Yes. 2) Not that I know of. In the only three cases I'm aware of, the most recent edit had been at least a few days earlier.
A similar bug has happened at the German Wikipedia - several articles only linked to [[de:Vorlage:MediaWiki Noarticletext NS]]. A null edit helped. If you speak German, you can find some stuff about this at [[de:WP:FZW]].
(and their archives, of course)
Closing as WORKSFORME. I can't even begin to replicate this, with or without caching. I can only assume it was an issue with the cache that has long since been fixed.
