TYPO3 Core

Oh, I should mention that it just not works in backend context. In frontend it still seems to work. I've seen in this findByRelation() method is an if condition which checks the environment. Probably there is a bug in the else part, which represents the backend environment.

it seems that "else" is in sysext/core/Classes/Resource/FileRepository.php

Yes, I am talking about the FileRepository object and its findByRelation() method. It contains an if condition checking the environment (FE or BE). The FE part works. The BE part not. But just since 6.2.4. In 6.2.3 everything worked fine.

I can confirm this bug with TYPO 6.2.12. I am not able to get referenced files in a backend module with the findByRelation() function. The field i defined is a flexform field and not in the TCA. Might be the cause for this? I dont have the time at the moment to investigate this further.

Workaround is to get the relations manually.

I can confirm this Bug with TYPO3 6.2.13. I tried to load referenced files in a backend TemplaVoila hook, for display in the backend. No fileReferences are returned.

Bug still there in 6.2.14. I dont get the FE/BE else part anyways, TSFE is just used for enableFields. What about:

$enableFields = $this->getEnvironmentMode() === 'FE' && !empty($GLOBALS['TSFE']->sys_page) ?
    $GLOBALS['TSFE']->sys_page->enableFields('sys_file_reference', $GLOBALS['TSFE']->showHiddenRecords) :
    \TYPO3\CMS\Backend\Utility\BackendUtility::BEenableFields('sys_file_reference');

$references = $this->getDatabaseConnection()->exec_SELECTgetRows(
    'uid',
    'sys_file_reference',
    'tablenames=' . $this->getDatabaseConnection()->fullQuoteStr($tableName, 'sys_file_reference') .
    ' AND uid_foreign=' . (int)$uid .
    ' AND fieldname=' . $this->getDatabaseConnection()->fullQuoteStr($fieldName, 'sys_file_reference')
    . $enableFields,
    '',
    'sorting_foreign',
    '',
    'uid'
);
if (!empty($references)) {
    $referenceUids = array_keys($references);
}

Why does this have "Needs Feedback" set and is closed?

I just reported a bug #99442 which looks very much similar if not duplicate (though I noticed the problem in CLI context, not in BE context).