Bug #39891
closed
class.t3lib_compressor floods php error log on Windows
0%
Description
Such messages flood PHP error log on Windows:
[17-Aug-2012 11:11:13] http://www.domain.local/ - Core: Error handler (BE): PHP Warning: filesize() [<a href='function.filesize'>function.filesize</a>]: stat failed for D:/wamp/www/www.domain.local/typo3//be/typo3lang.js in d:\wamp\www\www.domain.local\typo3_src\t3lib\class.t3lib_compressor.php line 462 [17-Aug-2012 11:11:13] http://www.domain.local/ - Core: Error handler (BE): PHP Warning: filemtime() [<a href='function.filemtime'>function.filemtime</a>]: stat failed for D:/wamp/www/www.domain.local/typo3/s/xtheme-t3skin.css in d:\wamp\www\www.domain.local\typo3_src\t3lib\class.t3lib_compressor.php line 357
It happens on IIS and Apache. I noticed this behavior in TYPO3 versions 4.5.16, 4.6.9 and 4.6.12
I made a small patch for TYPO3 v.4.6.12 that helped me. Please, consider aplying this patch to the core.
Files
Updated by Michael Stucki over 12 years ago
- Status changed from New to Needs Feedback
- Complexity deleted (
easy)
Hey Tomasz,
good to know that you found a solution for this problem. However, the problem is actually still unclear to me:
- Is there a problem with filesize() & filemtime()?
- Does the filename contain forbidden characters?
- Maybe the filename is too long?
Please try to find that out and let me know about it.
Thanks in advance!
- michael
Updated by Tomasz Krawczyk over 12 years ago
Michael,
The problem occurs always when the file doesn't exist in all functions using stat(). I had made test script asking for not existing file and always had this warnings.
On Windows I always avoid national characters in file names. Beside compressed files was .css and .js - generated by TYPO3.
I tested this on Windows Server 2003 and Windows XP. The file length is not a problem.
Tomek
Updated by Michael Stucki over 12 years ago
If the file is not existing, something else must be going wrong. To me it still looks like your fix is just working around symptoms but not resolving the real problem.
Can you please investigate a little more?
Can anyone else reproduce the problem using Windows?
Updated by Tomasz Krawczyk about 12 years ago
Michael,
I think, the problem occured only when I was developing some extension. It doesn't happen now. It looks it was my fault.
The bug may be closed.
Updated by Michael Stucki about 12 years ago
- Status changed from Needs Feedback to Resolved
Alright, thanks for your feedback.
Updated by