Last modified: 2009-05-13 18:53:45 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 8199 - Bug when using colon in ParserFunction #ifeq:
Bug when using colon in ParserFunction #ifeq:
Status: RESOLVED DUPLICATE of bug 12974
Product: MediaWiki extensions
Classification: Unclassified
ParserFunctions (Other open bugs)
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2006-12-09 14:51 UTC by Mark Clements (HappyDog)
Modified: 2009-05-13 18:53 UTC (History)
1 user (show)

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


Description Mark Clements (HappyDog) 2006-12-09 14:51:35 UTC
If I use the following parser code in a category sub-page, e.g.

 <nowiki>[[{{#ifeq: {{NAMESPACE}} | Category

I would expect a link back to the root page (Category:Test):

 [[:Category:Test]] (wiki code: <nowiki>[[:Category:Test]]</nowiki>)

Instead I get:


Which, in wiki code is : 


In other words, a newline seems to be inserted before the colon, causing it to
be treated as a blockquote.

This may also affect the other functions, and other symbols, e.g. *.

NB - There doesn't seem to be a ParserFunctions component, so I've put this in
Comment 1 Mark Clements (HappyDog) 2006-12-09 14:52:40 UTC
PS - Sorry about the <nowiki>'s in the above comment - didn't know how it would
Comment 2 Mark Clements (HappyDog) 2006-12-09 14:55:06 UTC
Also discussed (with slightly more correct examples) at
Comment 3 Chris Sherlock 2007-02-08 06:03:59 UTC
Even easier way of repro-ing this. Type in:

;Text:more text
Comment 4 Jelte (WebBoy) 2008-08-11 19:48:59 UTC

*** This bug has been marked as a duplicate of bug 10687 ***
Comment 5 Splarka 2009-05-13 18:53:45 UTC

*** This bug has been marked as a duplicate of bug 12974 ***

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