TYPO3 Core

Can be confirmed with Typo3 4.4.7

I have the same warnings in the php log file and in the BE. My environment is: TYPO3 v 4.5.3, PHP 5.3.6 OS: Windows Server 2003, IIS 6. My warnings occur when functions filesize() and filemtime() are used in class.t3lib_compressor.php line 341. It happens not only with atibility.js file but also with many other js and css files.

The PHP documentation sais that those 2 functions fail when file doesn't exist. So, I made simple test. When I made test.php file executing filesize() and filemtime() with non existing file as a parameter then I saw the same warning. There is no warning if the file exists.

In my xclass in the t3lib_compressor::compressJsFile() and t3lib_compressor::compressCssFile() methods I changed fourth line from:

$unique = $filenameAbsolute . filemtime($filenameAbsolute) . filesize($filenameAbsolute); 

to:

        if( file_exists($filenameAbsolute) )
            $unique = $filenameAbsolute . filemtime($filenameAbsolute) . filesize($filenameAbsolute);
        else
            $unique = $filename . strval( rand(0, 100000) ); 

I know my solution is ugly. So, please, core developers review my patch.

Ernesto, I implemented your patch, thought about its implications and tested. Unfortunately, now I get the same warnings as before, but in TemplaVoila:
Core: Error handler (BE): PHP Warning: filesize(): stat failed for /var/www/html/typo3/js/extjs/ux/flashmessages.js in /var/www/html/typo3_src-4.5.3/t3lib/class.t3lib_compressor.php line 341

The header comment of the function says only "Finds the relative path to a file, relative to the TYPO3_mainDir", but it does not say how it expects the input file name! And so, other extension programmers got used to its current behaviour and passed file names relative to PATH_site (e.g. "t3lib/js/extjs/ux/flashmessages.js" for TV).

I looked again why this happens here with linkvalidator and found out that the backPath of the template object is set AFTER calling setModuleTemplate, which results in the error. I've created bug report #28255 for this.

Alexander, Thomas, are you also using linkvalidator and can you relate the log warnings to the display of the linkvalidator report in the backend?

So, I guess the reason for this error is neither the compressor nor the template class as I assumed earlier but lies in the extensions using either the template class or addJsFile of the renderer in a wrong way. Therefore, I vote for a won't fix.