Issue Feature Under Review

#108009EXT:reports uses File Storage ID for export files path instead of the folder name

Riccardo De Contardi 11/07/25, 15:25 updated 11/09/26, 20:37

Description

If you use EXT:impexp to save some export file (as .xml files for example) you will end up with files inside a subfolder _temp_/importexport/ of your default storage (or the default user storage).

These files are listed on the “security > XML/T3D export files” section of the ext:reports module like this:

1:/user_upload/_temp_/importexport/T3D_tree_PID1491_L0_2025-08-12_11-11.xml

See attached file.

It would be nice if the actual storage folder name (e.g. “fileadmin” could be used instead of its ID which does not make much sense for the user

I think that the lines involved are in typo3/sysext/reports/Classes/Report/Status/SecurityStatus.php, function getExportedFilesStatus()

$queryBuilder = GeneralUtility::makeInstance(ConnectionPool::class)->getQueryBuilderForTable('sys_file');
        $exportedFiles = $queryBuilder
            ->select('storage', 'identifier')
            ->from('sys_file')
            ->where(
                $queryBuilder->expr()->like(
                    'identifier',
                    $queryBuilder->createNamedParameter('%/_temp_/importexport/%')
                ),
                $queryBuilder->expr()->or(
                    $queryBuilder->expr()->like(
                        'identifier',
                        $queryBuilder->createNamedParameter('%.xml')
                    ),
                    $queryBuilder->expr()->like(
                        'identifier',
                        $queryBuilder->createNamedParameter('%.t3d')
                    )
                ),
            )
            ->executeQuery()
            ->fetchAllAssociative();

        if (count($exportedFiles) > 0) {
            $files = [];
            foreach ($exportedFiles as $exportedFile) {
                $files[] = '<li>' . htmlspecialchars($exportedFile['storage'] . ':' . $exportedFile['identifier']) . '</li>';
            }
,,,

Marked as “Could have” as the issue is a quite low-priority feature request and not an actual bug.

Reviews 1

Files 1

History 13