Proposed by Erik on Commons-l; there seemed to be consensus about it, I'm unsure if more is needed.
Version: unspecified
Severity: enhancement
URL: https://commons.wikimedia.org/w/index.php?title=Commons:Village_pump/Proposals&oldid=86822276#Enabling_SearchExtraNs_extension
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Dereckson | T45329 Enable SearchExtraNs extension on Commons | |||
| Resolved | Dereckson | T45848 Deploy and review SearchExtraNs extension |
Please discuss the idea on Wikimedia Commons village pump.
I reviewed the thread and the only consensus I read is "include the namespace Category: to the default quick search" (e.g. solving bug 30323).
Discussion is opened on COM:VPP.
https://commons.wikimedia.org/wiki/Commons:Village_pump/Proposals#Enabling_SearchExtraNs_extension
I wonder if instead of a tiny code hooking at SearchAfterNoDirectMatch, we shouldn't implement this in core.
(In reply to comment #6)
Ok, let's enable it so.
[ Taking this bug. ]
Ideally it needs at least minimal i18n (a description) and something at https://www.mediawiki.org/wiki/Extension:SearchExtraNS to link to
Dereckson created the page https://www.mediawiki.org/wiki/Extension:SearchExtraNS
Looking at the PHP code, there are no strings to i18n. Where should the description and translations be written?
Jean-Fred: the description of our extensions can be translated too, with the {{desc}} parameter.
I'm not in an hurry on this matter, as we're entering the datacenter migration week. http://blog.wikimedia.org/2013/01/19/wikimedia-sites-move-to-primary-data-center-in-ashburn-virginia/
I prepared a config change to first deploy the extension to http://commons.wikimedia.beta.wmflabs.org/ first and if all is okay, I will then prepare the config change for Wikimedia Commons.