Last modified: 2014-02-20 21:39:05 UTC
https://commons.wikimedia.org/w/index.php?title=Special%3ASearch&profile=advanced&search=MediaWiki%3AVisualFileChange.js&fulltext=Search&ns2=1&redirs=1&profile=advanced Is the search string. I want results in the user-namespace but instead I get only results for the MediaWiki-namespace because search "thinks" it must be smart and override my setting. Results: * MediaWiki:VisualFileChange.js * MediaWiki:VisualFileChange.js/exec.js * [...] * MediaWiki:JSONListUploads.js Not one result in user namespace Expected: Only search results in user namespace or at least only a few in MW-Namespace.
(In reply to comment #0) > Expected: > Only search results in user namespace or at least only a few in MW-Namespace. I would say no results from other namespaces, only the ones selected by the user. That is why the user is selecting specific namespaces in the advanced search, right? PS: We are writing a scenario to check this problem, in the context of https://www.mediawiki.org/wiki/QA/Browser_testing/Search_features
[Merging "MediaWiki extensions/Lucene Search" into "Wikimedia/lucene-search2", see bug 46542. You can filter bugmail for: search-component-merge-20130326 ]
Verified as an issue in CirrusSearch. Recategorising.
The namespace: thing is supposed to override the clicking. Changing it too much is going to cause trouble with people that rely on it or the behaviors that stem from it (stuff like the prefix url parameter). If we're going to change it I'd advise at a minimum the prefixes continue to override the "Content pages" tab. It'd probably be safer for them to override all tabs but Advanced.
I think it's actually an issue in core, not Cirrus or any other search backend.
(In reply to comment #4) > The namespace: thing is supposed to override the clicking. Changing it too > much is going to cause trouble with people that rely on it or the behaviors > that stem from it (stuff like the prefix url parameter). If we're going to > change it I'd advise at a minimum the prefixes continue to override the > "Content pages" tab. It'd probably be safer for them to override all tabs > but > Advanced. That makes sense. If someone goes to the trouble to manually configure what namespace they're searching in, then types in "MediaWiki:Foo" as their search query, they're not expecting search to override their manually selected namespaces. In most other cases where they've not chosen their namespaces manually, it makes sense for this override to take place.
But, how are you expecting to determine if the user manually adjusted the checkboxes or simply went to https://commons.wikimedia.org/wiki/Special:Search and expected the manually typed namespace to override them? And if you are thinking "let's check if typed on skin search box or Special:search", that would be very inconsistent, as searching «MediaWiki:VisualFileChange.js» in the skin, then pressing Search again, would lead to a completely different result. PS: You can search results in user ns only by issuing "MediaWiki:VisualFileChange.js". Maybe the fix shall be adding a «Did you mean… ?» for this kind of conflicts.
