Last modified: 2011-01-25 01:04:11 UTC
It says "Results 1-2 of 2" but I swear I only see one item: $ w3m -dump "http://commons.wikimedia.org/wiki/Special:Search?search=Intrauterine&fulltext=Search" Results 1-2 of 2 ‧ Image:Danshan Nongguang Village Bulletin board.jpg ...ks" [Note: Sancha: check for pregnancy, check for intrauterine loop, and check for illness. End note.] Of the 34... Relevance: 100.0% - 1.3 KB (197 words) - 20:09, 1 January 2007
Wikimedia Commons uses Lucence 2.0 -> moving this bug to extensions.
I see two! Results 1-2 of 2 * Image:Danshan Nongguang Village Bulletin board.jpg Relevance: 100.0% - - * Image:English language icon.svg Relevance: 95.4% - -
Yes, today using the "IE" browser in the public library, I see two too. Therefore, the HTML sent is probably very browser dependent, etc. Taking a look at the HTML... not today here in the public library... next week I will take a look...
Ah ha, luckily I had and old copy in WWWOFFLE that shows the problem which occured that day: <!-- querying /search/commonswiki/Intrauterine?namespaces=0%2C6%2C9%2C12%2C14&offset=0&limit=20&case=ignore --> <hr /><strong>Results 1-2 of 2</strong><div style="text-align: center;"></div><ul><li style="padding-bottom: 1em;"><a href="/wiki/Image:Danshan_Nongguang_Village_Bulletin_board.jpg" title="Image:Danshan Nongguang Village Bulletin board.jpg">Image:Danshan Nongguang Village Bulletin board.jpg</a><br /><small>...ks" [Note: Sancha: check for pregnancy, check for <span class='searchmatch'>intrauterine</span> loop, and check for illness. End note.] Of the 34...</small> <br /><span style="color: green; font-size: small;">Relevance: 100.0% - 1.3 KB (197 words) - 20:09, 1 January 2007</span></li> <!--Broken link in search results: English_language_icon.svg--> </ul><hr /><div style="text-align: center;"></div><br /><br /> <form id="powersearch" method="get" action="/wiki/Special:Search"> Search in namespaces: Therefore if the error "Broken link in search results" occurs, that fact is hidden in HTML comments, but the counter is shown to the user incremented anyway. Therefore don't increment the counter you show to the user unless you intend to show him the error too, (which would be best too.)
Looks like the search result gets hidden when you're logged in, but not when you're logged out. This would be a side-effect of the disabling of result text highlighting for logged-out visitors; the revision text doesn't get loaded, so there's no existence check performed.
Created attachment 4474 [details] Screenshot showing visible HTML comment I thought the incorrect # of search results was due to the fact that it was the result from all namespaces, but it only shows you results from certain namespaces. Anyway, I'm not sure if what I experienced today is the same thing or what. I searched on Commons for "crowds" and before the second result I saw this: <!--Broken link in search results: Overflow--Crowds.jpg--> they were < ascii symbols rather than proper angle brackets.
I don't know whether it is correlated, but http://de.wikipedia.org/wiki/Spezial:Suche?search=Benutzerseite+Homepage&go=Artikel shows "1–4 von 4" while displaying only three hits. One is commented out (?) as: | <!-- missing page ArEb.schneider--> This happens when logged in as well as logged out.
Oh, and of course http://de.wikipedia.org/wiki/Spezial:Suche/ArEb.schneider.
(@Tim Landsheidt) I think that is a separate bug - this one is to do with broken links in search results. For the missing pages, see bug 13792.
There are two issues here: a missing ArticleDelete hook call (fixed in r32742), and the lucene-search issue related to bug 12237 and bug 13792 (when some deletions don't get processed). Both of these have been fixed, but need an index rebuild / system update.
Mass close WONTFIX open Lucene Search issues because extension Lucene Search was removed, and replaced by MWSearch. Please set to REOPENED if behaviour still exists with a another component, and update the domain.
Mass REOPEN after discussion with Robert. Domain: Wikimedia/lucene-search-2. Assigned to maintainer.
This is fixed since we switched to new servers / new lucene-search version.