Commit graph

110 commits

Author SHA1 Message Date
Aryeh Gregor 1c902f410c (bug 6199) Generate error for unbalanced <ref>s
This basically uses the patch I posted to that bug two years ago.  It's crude, but it should avoid the most common false positives while hopefully not causing too many false negatives.  It should be possible to refine it to avoid even more false negatives, but for the time being, this will at least prevent most of the constant headaches that newbies get when chunks of articles vanish because they forgot a closing </ref>.
2008-09-18 17:16:10 +00:00
Siebrand Mazeland 5bca5776eb * Fix common spelling error (seperate -> separate)
* Fix two more spelling errors in Translate extension messages
2008-09-15 20:28:25 +00:00
Aaron Schulz 6c824fd58d Consistent return array to avoid notices 2008-09-12 14:41:23 +00:00
Alex Z. e7454069b6 (bug 15517) - Use correct error message if group parameter is allowed (message already existed but was apparently unused). 2008-09-09 03:55:54 +00:00
Brion Vibber e8786ea9b5 Revert r38669 for now (Cite extension "add format=a option for alphabetic format").
It isn't obviously clear how this is meant to be used, and there are no test cases for the newly added mode.
Newly added code doesn't match our code standards, making it harder to read, and contains mysterious things like "$argv=array_merge($argv);" which seem a bit odd.
2008-08-08 19:11:31 +00:00
Steve Sanbeg a4ce1077d1 add format=a option for alphabetic format 2008-08-05 21:52:26 +00:00
Aryeh Gregor 9fcce4febe Delete Cite::validateName(). Use Xml::escapeId() instead. All parser tests pass. 2008-07-30 21:23:43 +00:00
Shinjiman c2d03f184b * (bug 14216) Grouping references link displays are urlencoded instead rendering the normal text
patch by fdcn
2008-06-18 18:42:52 +00:00
Roan Kattouw 2986a5a8d2 Cite: Fix bug 11224 (finally): in some obscure cases (notably when parsing for an anon without edit rights), Parser::clearState() somehow got in the call path of Cite::ref(), clearing the Cite state in mid-parse every time. I've worked around this by refusing to clear state if the state indicates we're in the middle of parsing something, but this is probably not a proper fix as there seems to be something deeply evil going on in the Parser (big surprise) causing it to clear state haphazardly. Anyone interested in further investigation should read the backtrace I posted on bug 11224 2008-06-16 14:04:39 +00:00
Brion Vibber 933caf85db Update a bunch of extensions to avoid unstubbing $wgParser early for setHook() on current MW versions. 2008-06-06 20:38:04 +00:00