Issue Bug Closed

#107907Handle package path also in getFileAbsFileName

Benjamin Kott 10/29/25, 12:02 updated 12/02/25, 12:04

Description

A change in the relation chain causes certain path types to be processed earlier than before — for example, in the PageRenderer during preProcessHooks such as:

$GLOBALS[‘TYPO3_CONF_VARS’][‘SC_OPTIONS’][‘t3lib/class.t3lib_pagerenderer.php’][‘render-preProcess’]

Previously, these hooks received the initially set path values.
Now, we are seeing migrated PKG: path identifiers in addition to the traditional file paths.

This is a significant change because there is currently no migration handling for these identifiers — they are being checked manually.
It’s likely an unintended side effect, but it exposes a gap in supporting the new syntax.

Example

New format:
PKG:bk2k/bootstrap-package:Resources/Public/Scss/bootstrap5/theme.scss

Old format:
EXT:bk2k/bootstrap-package/Resources/Public/Scss/bootstrap5/theme.scss

The only difference is the prefix (PKG instead of EXT) and the separator (: instead of /).
The old format was previously supported throughout the system.

Many usages rely on:
GeneralUtility::getFileAbsFileName($file);

Paths like EXT:<path> typically cannot be used directly.<br>As a result, all calls to getFileAbsFileName() — commonly found in extension code — are now affected.</path>

Updating these would require substantial developer effort without adding business value, purely to maintain compatibility.

Reviews 2