Bug #60396
closed
Compressed and concatenated CSS files missing
0%
Description
Since we used the following TS options
- compress and concatenate CSS and JS
#config.compressJs = 1
#config.compressCss = 1
#config.concatenateJs = 1
#config.concatenateCss = 1
on some pages the compressed an concatenated CSS are missing (till we clear the cache). The problem is that it is not reproduceable. The pages differ and we only find out if a user or editor points out that a page is delivered with missing CSS styles.
Updated by Markus Klein over 10 years ago
- Status changed from New to Needs Feedback
Hi Klaus,
thanks for your report. Maybe post this issue on the mailing lists/forums. Chances are higher you get meaningful responses there.
Since this is not reproducable and I never heard about such a problem, the issue is a bit wrong placed in the bug-tracker.
We can't fix anything if we don't know how it breaks. :-/
I guess you tested this on 6.2.4, if not consider updating asap please.
Updated by Klaus Hinum over 10 years ago
Well it is happening quite often, looks like every 30th page of our site is affected. Still on 6.2.3 though as upgrade will occure next week, but I do not find any bug fix mentioned in the 6.2.4 release notes.
I wonder why the compressed files are missing, e.g.
typo3temp/compressor/merged-cc411e5ddb8e7234ea9ab39dc4366fca-86ef4a25bd01a8a8926ab15ab691676b.css?1405674327
shouldnt these files be the same on each call? Why create new named ones when the cache is cleared and what is deleting the old files? Could it be that if a page is called with different calls (we use simulate static documents) so e.g. abc.123.0.html and def.123.0.html that the first merged css is deleted?
Updated by Markus Klein over 10 years ago
I'm not aware of a feature that is actually removing files from typo3temp (except the Install Tool).
The filename of the the merged files is created from these parameters by md5() hashing them:
$filenameAbsolute . $fileStatus['mtime'] . $fileStatus['size']
So new files are only created if the filename changes or if the file is modified.
Updated by Klaus Hinum over 10 years ago
Then the question is why the file is not generated sometimes (it definately did not change anything on the pages that should trigger new MD5 hashes).
Updated by Markus Klein over 10 years ago
Maybe because it is not necessary to create the file if the entire pages comes from cache anyway. TYPO3 does not expect that the files are deleted without clearing the cache as well.
Updated by Klaus Hinum over 10 years ago
Well the file should not be deleted by anything as you wrote above (I definately did not delete it manually or using the Install Tool). So either something is deleting the cache file or it was not created properly.
Updated by Markus Klein over 10 years ago
As I said there is no logic I'm aware of that deletes those files. Also not when clearing the cache.
If you do delete such a file manually, then you will need to clear the cache.
If the file could not be created, then you should find some warning in the logs. (either TYPO3 log or webserver/php log)
Updated by Alexander Opitz almost 10 years ago
- Status changed from Needs Feedback to Closed
No feedback within the last 90 days => closing this issue.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.