Last modified: 2007-02-18 11:58:21 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T7045, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 5045 - Dates in [[yyyy-mm-dd]] format immediately followed by <ref> don't work
Dates in [[yyyy-mm-dd]] format immediately followed by <ref> don't work
Status: VERIFIED FIXED
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
unspecified
All All
: Normal normal with 2 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
http://en.wikipedia.org/w/index.php?t...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-02-19 21:19 UTC by Wikipedia:en:User:Paddu
Modified: 2007-02-18 11:58 UTC (History)
0 users

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


Attachments

Description Wikipedia:en:User:Paddu 2006-02-19 21:19:34 UTC
In the linked URL, [[2006-01-27]]<ref> is rendered as:

          [1]
2006-01-27

with a red link to (the inexistent article) [[2006-01-27]], instead of blue
links to [[January 27]] and [[2006]].

Not sure if this is a problem with the Cite extension or date rendering in
MediaWiki.
Comment 1 Wikipedia:en:User:Paddu 2006-02-19 21:20:48 UTC
(In reply to comment #0)
> In the linked URL, [[2006-01-27]]<ref> is rendered as:
> 
>           [1]
> 2006-01-27

I meant 2006-01-27 followed by [1] as subscript.
Comment 2 Wikipedia:en:User:Paddu 2006-02-25 14:06:13 UTC
Sorry for the spam. I did mean superscript instead of subscript.
Comment 3 Ævar Arnfjörð Bjarmason 2006-02-26 22:17:51 UTC
This is a parser issue and not an issue with Cite, and it probably affects all
parser hooks in that way.
Comment 4 Jondor 2007-01-16 22:05:56 UTC
Now, almost 11 months after Ævar's statement, the URL linked above does not show
the erroneous behavior described in the bug report. I take that to mean that the
bug is fixed by means of resolving the general issue regarding the parser. I
changed this bug's status accordingly.

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


Navigation
Links