Issue Bug Closed

#110078BackendUtility::getModuleData() uses null as array offset — deprecated in PHP 8.4+, causes exception in Install Tool

Volker Golbig 06/18/26, 14:29 updated 08/11/26, 08:50

Description

BackendUtility::getModuleData() in typo3/cms-backend uses null as an array offset, which triggers E_DEPRECATED in PHP 8.4+ and E_USER_DEPRECATED in PHP
8.5.

Affected file: typo3/sysext/backend/Classes/Utility/BackendUtility.php, line 2240
Problematic code:
if (is_array($settings[$key] ?? null) || !isset($MOD_MENU[$key][$settings[$key] ?? null])) {
The second operand uses $settings[$key] ?? null as an array offset ($MOD_MENU[$key][null]), which PHP 8.4 deprecated with:
▎ PHP Deprecated: Using null as an array offset is deprecated, use an empty string instead 
Impact:
When the TYPO3 Install Tool runs with the “Debug” configuration preset (SYS/exceptionalErrors = 12290, which includes E_DEPRECATED = 8192), this
deprecation notice is converted to an exception (error code #1476107295), completely breaking the “Database Analyzer” (DB Check) and potentially other
Install Tool sections that call BackendUtility::getModuleData().
The error message shown is: 
(1/1) #1476107295 TYPO3\CMS\Core\Error\Exception
PHP Runtime Deprecation Notice: Using null as an array offset is deprecated,
use an empty string instead in …/BackendUtility.php line 2240
Fix:
Replace ?? null with ?? ‘’ in the isset() call:
// Before
if (is_array($settings[$key] ?? null) || !isset($MOD_MENU[$key][$settings[$key] ?? null])) {
// After
if (is_array($settings[$key] ?? null) || !isset($MOD_MENU[$key][$settings[$key] ?? ‘’])) {
This is safe because PHP converts null array keys to ‘’ internally anyway.
Note: Commit a51ceaa in the main branch already addresses this class of deprecations under the title “Mitigate ‘Using null as an array offset is 
deprecated’”, but this specific line in BackendUtility.php has not yet been backported to the 13.4 LTS branch.
TYPO3 version: 13.4.32
PHP version: 8.4 / 8.5

Reviews 2

History 45

  1. Garvin Hicking commented and changed status New Accepted <span data-processor="relativetime" data-value="2026-06-18T15:52:29+00:00" > 06/18/26, 15:52 </span>

    Hi!

    Thank you, this should have been fixed with https://review.typo3.org/c/Packages/TYPO3.CMS/+/93512 #109461 but somehow it seems that the backport did not contain the same change as done to V14.

    Will have to investigate.

  2. Gerrit Code Review pushed patch set 1 for 13.4 to change 94529 status Accepted Under Review <span data-processor="relativetime" data-value="2026-06-18T17:44:43+00:00" > 06/18/26, 17:44 </span>

  3. Garvin Hicking commented <span data-processor="relativetime" data-value="2026-06-18T17:49:06+00:00" > 06/18/26, 17:49 </span>

    Hey @machwert – could you check out the backport patch attached to this? Obviously I failed at the proper backport and I’m sorry for it!

  4. Garvin Hicking commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2026-06-22T07:30:13+00:00" > 06/22/26, 07:30 </span>

    Applied in changeset commit:0727294f727ebe5133a6d1eeeb3b55c282e6f341.