Last modified: 2008-03-21 21:42:26 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 11742 - Problem with namespace specific search
Problem with namespace specific search
Product: MediaWiki extensions
Classification: Unclassified
InputBox (Other open bugs)
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on: 7318
  Show dependency treegraph
Reported: 2007-10-22 20:53 UTC by Mark Pasman
Modified: 2008-03-21 21:42 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description Mark Pasman 2007-10-22 20:53:20 UTC
+++ This bug was initially created as a clone of Bug #7318 +++

I also want the extension to search in one or more specific namespaces and according to the extension description this can be done but it does not work.

When namespaces are defined the search must be "searchx". If no namespaces are defined it must be "fulltext". I guess some code must be added around line 132:
<input type='submit' name="fulltext" class="searchboxSearchButton" value="{$this->searchbuttonlabel}" />

The above does not work for what i want so i changed it to:
<input type='submit' name="searchx" class="searchboxSearchButton" value="{$this->searchbuttonlabel}" />

then it works (for me) but then someone else got a problem. Can you fix it for all of us?

Comment 1 Brion Vibber 2008-03-21 21:42:26 UTC
Assuming this would have been fixed with core UI by r32302; hard to tell though as the example code is gone at the linked URL.

Resolving as FIXED; please reopen with further detail if it's still a problem.

Note You need to log in before you can comment on or make changes to this bug.