From fa6cd2f9b79a9a3a2e423b92365977287ea274d6 Mon Sep 17 00:00:00 2001 From: Pedro Amorim Date: Mon, 2 Sep 2024 14:51:31 +0000 Subject: [PATCH] Bug 37810: Consider ServiceActive on status response Some SUSHI providers return ServiceActive instead of the documented Service_Active: https://countermetrics.stoplight.io/docs/counter-sushi-api/f0dd30f814944-server-status This ensures the test connection does not fail regardless of what is used Signed-off-by: David Nind Signed-off-by: Nick Clemens Signed-off-by: Martin Renvoize --- Koha/ERM/EUsage/UsageDataProvider.pm | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Koha/ERM/EUsage/UsageDataProvider.pm b/Koha/ERM/EUsage/UsageDataProvider.pm index d70755ae5c..cdb82e31d5 100644 --- a/Koha/ERM/EUsage/UsageDataProvider.pm +++ b/Koha/ERM/EUsage/UsageDataProvider.pm @@ -294,10 +294,10 @@ sub test_connection { my $status; if ( ref($result) eq 'ARRAY' ) { for my $r (@$result) { - $status = $r->{Service_Active}; + $status = $r->{Service_Active} // $r->{ServiceActive}; } } else { - $status = $result->{Service_Active}; + $status = $result->{Service_Active} // $result->{ServiceActive}; } if ($status) { -- 2.39.5