From c39ba9706ae44ad7f302957e51cd2cef3d9a7242 Mon Sep 17 00:00:00 2001 From: Tim Starling Date: Mon, 27 Aug 2012 10:40:27 +1000 Subject: [PATCH] Fix exception on parse due wfMsgExt() -> wfMessage() Replacing wfMsgExt() with wfMessage() in 4e1ccf0 causes an exception on parse when the defaults are used for $current and $max. I don't know if there are other similar fatal errors caused by that set of commits. Change-Id: I84cfdede844bb2dd3c106721b972ed1cd8bfe480 --- includes/parser/Parser.php | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/includes/parser/Parser.php b/includes/parser/Parser.php index 489451a2ef..5f211b183b 100644 --- a/includes/parser/Parser.php +++ b/includes/parser/Parser.php @@ -3086,7 +3086,7 @@ class Parser { * @param $max int|null Maximum allowed, when an explicit limit has been * exceeded, provide the values (optional) */ - function limitationWarn( $limitationType, $current = null, $max = null) { + function limitationWarn( $limitationType, $current = '', $max = '' ) { # does no harm if $current and $max are present but are unnecessary for the message $warning = wfMessage( "$limitationType-warning" )->numParams( $current, $max ) ->inContentLanguage()->escaped(); -- 2.20.1