Last modified: 2006-03-02 02:35:39 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 3328 - Nogomatch parameter $1 returns extraneous introductory colon
Nogomatch parameter $1 returns extraneous introductory colon
Product: MediaWiki
Classification: Unclassified
Interface (Other open bugs)
All All
: Normal trivial with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2005-09-01 03:21 UTC by Muke Tever
Modified: 2006-03-02 02:35 UTC (History)
0 users

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


Description Muke Tever 2005-09-01 03:21:46 UTC
When a failed go brings up the Mediawiki:Nogomatch 
message, the value of the query, $1, is prepended 
by a colon.  

Why is this here?  I thought it might be to 
indicate the main namespace, but even if another 
namespace is given in the go-search the colon is 
there.  This might make sense if for some reason 
someone wanted to transclude the pagename being 
searched for in this message with {{$1}} -- but 
that would be silly in a message telling you $1 
doesn't exist.

At any rate, is there any way to remove this, so 
$1 can be cleanly displayed to the user?  (I tried 
'$2' which was the former solution, but this only 
comes up blank.)
Comment 1 Rob Church 2006-03-02 00:22:47 UTC
At the moment, it's because if someone's searching for an image or category
description page that doesn't exist, the software will attempt to render the
link inline.
Comment 2 Brion Vibber 2006-03-02 02:35:39 UTC
It's not extraneous, so closing bug as INVALID.

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