Issue Task Closed

#105898Extension scanner should find usages of magic strings like TYPO3_MODE

Garvin Hicking 01/07/25, 21:38 updated 08/12/25, 14:36

Description

An upgrade to TYPO3 v12 can be painful when backend or frontend
modules (or even the Database Analyzer) bails out with a white
page. Usually this would lead to inspection of logfiles,
checking if PHP’s `error_reporting` or `display_errors` is
not properly set, looking for PHP/Webserver coredumps,
problems in HTTP headers, CSP errors and much more, just
to find out that a

`defined(‘TYPO3_MODE’) or die()`

was left in some PHP file of an extension, which needs
to be replaced with `TYPO3` (see #92947 and #96107).

The Extension Scanner only scanned for the full
PHP constant usage before.

With this patch, these “magic strings” can now also
be scanned and reported, making debugging of a
malfunctioning upgrade much easier for developers
and especially integrators.

Reviews 3

History 312

  1. Garvin Hicking commented and changed status Under Review Resolved done 0 % 100 % <span data-processor="relativetime" data-value="2025-01-09T14:30:15+00:00" > 01/09/25, 14:30 </span>

    Applied in changeset commit:0616a66d8bd184fff4751f9b1ecb5364b5487b86.