From a22de4ce99a4cff2426e0145af22204b97f4b288 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?David=20Mudr=C3=A1k?= Date: Tue, 13 Nov 2012 11:24:55 +0100 Subject: [PATCH] MDL-36494 Do not display a debugging message about invalid update info It turned out that this well-meant debugging message just caused a lot of false alarm with no good reason. It seems to be better just ignore it at the moment. --- lib/pluginlib.php | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/lib/pluginlib.php b/lib/pluginlib.php index e8cb001ce7a..fa41e3ad3a1 100644 --- a/lib/pluginlib.php +++ b/lib/pluginlib.php @@ -913,7 +913,10 @@ class available_update_checker { $this->recentfetch = $config->recentfetch; $this->recentresponse = $this->decode_response($config->recentresponse); } catch (available_update_checker_exception $e) { - debugging('Invalid info about available updates detected and will be ignored: '.$e->getMessage(), DEBUG_ALL); + // The server response is not valid. Behave as if no data were fetched yet. + // This may happen when the most recent update info (cached locally) has been + // fetched with the previous branch of Moodle (like during an upgrade from 2.x + // to 2.y) or when the API of the response has changed. $this->recentresponse = array(); }