From bcb6429372f911bb1f405ac57e934df08adf2621 Mon Sep 17 00:00:00 2001
From: Jackmcbarn <jackmcbarn@gmail.com>
Date: Thu, 14 Jan 2016 12:10:33 -0500
Subject: [PATCH] Fix protectionexpiry using the wrong page

Change-Id: I0d8cfd68a735fbcdd32a000ef47e6922a816968e
---
 includes/parser/CoreParserFunctions.php | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/includes/parser/CoreParserFunctions.php b/includes/parser/CoreParserFunctions.php
index d25d11a6db..91b6080c32 100644
--- a/includes/parser/CoreParserFunctions.php
+++ b/includes/parser/CoreParserFunctions.php
@@ -813,7 +813,7 @@ class CoreParserFunctions {
 			$titleObject = $parser->mTitle;
 		}
 		if ( $titleObject->areRestrictionsLoaded() || $parser->incrementExpensiveFunctionCount() ) {
-			$expiry = $parser->mTitle->getRestrictionExpiry( strtolower( $type ) );
+			$expiry = $titleObject->getRestrictionExpiry( strtolower( $type ) );
 			// getRestrictionExpiry() returns false on invalid type; trying to
 			// match protectionlevel() function that returns empty string instead
 			if ( $expiry === false ) {
-- 
2.20.1