From 7a9f9b1dca9ac28a2962f9a3947c1ffeb40dd24d Mon Sep 17 00:00:00 2001 From: Marcus Schwemer Date: Fri, 5 Jul 2024 17:06:58 +0200 Subject: [PATCH] [BUGFIX] Provide a fallback for null values There might be situation, where the `explicit_allowdeny` column is null. (Probably very old installations, where the column had null as default. Providing an empty string as a fallback solves the issue. Related: in2code-de/powermail#1062 Related: in2code-de/powermail#1019 Signed-off-by: Marcus Schwemer --- Classes/Update/PowermailPermissionUpdater.php | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Classes/Update/PowermailPermissionUpdater.php b/Classes/Update/PowermailPermissionUpdater.php index a512b1788..1d136562c 100644 --- a/Classes/Update/PowermailPermissionUpdater.php +++ b/Classes/Update/PowermailPermissionUpdater.php @@ -113,7 +113,7 @@ protected function updateRow(array $row): void 'tt_content:list_type:powermail_pi1' => $pi1Replacement, ]; - $newList = str_replace(array_keys($searchReplace), array_values($searchReplace), $row['explicit_allowdeny']); + $newList = str_replace(array_keys($searchReplace), array_values($searchReplace), $row['explicit_allowdeny'] ?? ''); $queryBuilder = GeneralUtility::makeInstance(ConnectionPool::class)->getQueryBuilderForTable('be_groups'); $queryBuilder->update('be_groups') ->set('explicit_allowdeny', $newList)