TYPO3 Core

Looking into the class TYPO3.CMS.Core.Resource.ProcessedFile, I now understand that entries with name=NULL are valid: 'A file may also meet the expectations set in the configuration without any processing. In that case, the ProcessedFile object still exists, but there is no physical file directly linked to it. Instead, it then redirects most method calls to the original file object. The data of these objects are also stored in the database, to indicate that no processing is required. With such files, the identifier and name fields in the database are empty to show this.'

But that still doesn't explain why these entries are generated for processed files. However, I suspect something is wrong with the config of this particular site, as I tested the same bahaviour on another site (far less complex as far as extensions etc is considered), and there no 'wrong' entries are generated. I'll investigate further and report back on my findings.

If name is null and the identifier empty, what sould be the values of width and height? Shoudl they both be 0? I have seen this data and it broke the FE.

And there is also a fix concerning such entries:

https://review.typo3.org/#/c/39373/

Martin Kutschker wrote:

If name is null and the identifier empty, what sould be the values of width and height? Shoudl they both be 0? I have seen this data and it broke the FE.

Of course the width and height of the original file should be used, as it can be used without processing (and the record is merely a flag to show that no processing is necessary and the processing attempt does not have to be repeated over and over again).

We had this happen to a high extent (up to 20% of invalid records) on a very image-heavy site. It shows in the frontend as not rescaled images where the src-output of a <f:image>-Viewhelper has the original file instead of the processed file.

It can be seen in all Typo3-7.6 - instances that we have running so this is a bug with massive impact. Some instances use ImageMagick, some GraphicsMagick.

After 'clean up' -> 'clear processed files' in the InstallTool it would randomly happen again.

Here is a patch for typo3-7.6.4 (I am checking for the existence of 'identifier'):

diff -r typo3_src-7.6.4/typo3/sysext/core/Classes/Resource/ProcessedFileRepository.php typo3_src-7.6.4-processedFilePatched/typo3/sysext/core/Classes/Resource/ProcessedFileRepository.php
136,138c136,140
<             $this->databaseConnection->exec_INSERTquery($this->table, $insertFields);
<             $uid = $this->databaseConnection->sql_insert_id();
<             $processedFile->updateProperties(array('uid' => $uid));
---
>             if (isset($insertFields['identifier'])) {
>                 $this->databaseConnection->exec_INSERTquery($this->table, $insertFields);
>                 $uid = $this->databaseConnection->sql_insert_id();
>                 $processedFile->updateProperties(array('uid' => $uid));
>             }
154c156,158
<             $this->databaseConnection->exec_UPDATEquery($this->table, 'uid=' . (int)$uid, $updateFields);
---
>             if (isset($updateFields['identifier'])) {
>                  $this->databaseConnection->exec_UPDATEquery($this->table, 'uid=' . (int)$uid, $updateFields);
>             }

Sorry I did not check further. This is a workaround only. Finding the real culprit would be helpful of course.