Last modified: 2008-08-11 18:28:03 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 T14757, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 12757 - improperly closed references tag should result in an obvious error
improperly closed references tag should result in an obvious error
Status: RESOLVED DUPLICATE of bug 6199
Product: MediaWiki extensions
Classification: Unclassified
Cite (Other open bugs)
unspecified
All All
: Normal enhancement with 3 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
: patch, patch-need-review
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2008-01-23 15:21 UTC by Random832
Modified: 2008-08-11 18:28 UTC (History)
3 users (show)

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

Attachments
Proposed patch (2.15 KB, patch)
2008-04-16 14:43 UTC, Max Semenik 		Details
Changes due to introduction of Cite_body.php, tests (3.18 KB, patch)
2008-06-18 08:18 UTC, Max Semenik 		Details
Show Obsolete (1) Add an attachment (proposed patch, testcase, etc.)

Description Random832 2008-01-23 15:21:36 UTC 
Right now, if someone closes a <ref> tag with <ref> instead of </ref>, a lot of content gets shoved down into the reference, but there's no boldface red text to say what has gone wrong. My suggestion: if <ref> is detected inside a <ref> tag, it is an error; an error message should show up at the location of the <ref> tag.
Comment 1 Max Semenik 2008-04-16 14:43:05 UTC 
Created attachment 4824 [details]
Proposed patch
Comment 2 Low Sea 2008-04-25 08:06:57 UTC 
Please see this discussion related to this bug on WP --> http://en.wikipedia.org/wiki/Wikipedia:Bot_requests#Need_a_bot_to_find_corrupted_REFLIST_outputs.
Comment 3 Max Semenik 2008-06-17 16:01:54 UTC 
Please review, it's an easy fix.
Comment 4 Brion Vibber 2008-06-17 21:59:16 UTC 
Looks straightforward; this is a good candidate for adding a parser test case to make sure it doesn't regress. (to citeParserTests.txt)
Comment 5 Max Semenik 2008-06-18 08:18:15 UTC 
Created attachment 4997 [details]
Changes due to introduction of Cite_body.php, tests
Comment 6 Jelte (WebBoy) 2008-08-11 18:28:03 UTC 

*** This bug has been marked as a duplicate of bug 6199 ***
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links