Last modified: 2006-12-03 04:27:07 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 6770 - $1 in MediaWiki:Nogomatch has leading colon
$1 in MediaWiki:Nogomatch has leading colon
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
All All
: Normal trivial (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2006-07-21 14:54 UTC by Danny B.
Modified: 2006-12-03 04:27 UTC (History)
0 users

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


Description Danny B. 2006-07-21 14:54:32 UTC
1. $1 returns the searched text with leading colon. I wonder about needs, didn't
find any. It's not possible to simply write something like
"There's no page in Wikipedia with name $1"
because it confuses people when they search for "foo" and get
"There's no page in Wikipedia with name :Foo"
or searching for "Template:bar" returns
"There's no page in Wikipedia with name :Template:bar"

2. $1 used in one built-in template works, in other does not
When need to point to any log page the first idea is:
[{{fullurl:Special:Log|type=move&page=$1}} Move log]
but in case of $1 of more words (Lorem ipsum) it returns link going to log of
page "Lorem" with anchor text "ipsum Move log"
Ok, so apparently encoding needed:
[{{fullurl:Special:Log|type=move&page={{urlencode:$1}}}} Move log]
but it returns link going to log of page "$1" with anchor text "Move log"

Danny B.
Comment 1 Aryeh Gregor (not reading bugmail, please e-mail directly) 2006-07-21 19:30:08 UTC
Please file separate requests separately in the future.

1) It is a bit weird, yes.  Fair enough to leave it as a bug.

2) This is bug 6261.
Comment 2 Rob Church 2006-12-03 04:27:07 UTC
Ironed out when "nogomatch" was renamed to "noexactmatch"; the leading colon was
dropped and the message format changed.

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