Bug #88243
closed
Assets not cleared if excluded from concatenation
Added by Patrick Lenk about 5 years ago.
Updated over 4 years ago.
Description
Assets that are compressed and excluded from concatenation are not cleared from typo3temp/assets/compressed after clear frontend or all caches.
In my instance these files are explicit not concatenated with the main css or js files, because they only inserted on some pages and therefore not merged with the other css/js files to safe bandwidth.
I want to don't force the user to download all other main css/js files again and just add the additional plugin/module files dynamically. The main files are already well cached, so only the additional files have to downloaded and this increase performance. Because no new huge merged css/js file have to be generated.
The files are included with typoscript (includeJSFooter, includeCSS and excludeFromConcatenation).
After change the files that are not concatenated, i have to remove the compressed files in typo3temp manually.
- Target version changed from next-patchlevel to Candidate for patchlevel
Current workaround: Remove the outdated assets in typo3temp/assets/compressed directory on deployment with a composer post update command.
- Status changed from New to Needs Feedback
Hey,
if I understood correctly, your problem is that the files aren't regenerated, but that the - now unused - files remain in the folder. TYPO3 in general does not clear the asstes folder automatically, but you can do that via the Install Tool > Remove temporary assets.
After changes to your CSS/JS files, TYPO3 does not know exactly which files in assets/compressed it could delete (as the file names are calculated by mtime and size of the original - which changed in your case) and it does not know whether or not you have other parts accessing these resources.
Removing the assets like you do (or periodically using the install tool) is the valid solution to this issue.
Susanne Moog wrote:
Hey,
if I understood correctly, your problem is that the files aren't regenerated, but that the - now unused - files remain in the folder. TYPO3 in general does not clear the asstes folder automatically, but you can do that via the Install Tool > Remove temporary assets.
After changes to your CSS/JS files, TYPO3 does not know exactly which files in assets/compressed it could delete (as the file names are calculated by mtime and size of the original - which changed in your case) and it does not know whether or not you have other parts accessing these resources.
Removing the assets like you do (or periodically using the install tool) is the valid solution to this issue.
Hey Susanne, thanks for your Feedback. I think this issue can be closed.
I don't test it with the new AssetCollector in 10.3, maybe it works with the future way of inlcude assets directly in fluid.
Or this is a "missing" point in the site package documentation.
- Status changed from Needs Feedback to Closed
Ok, thanks for your answer, closing the issue. If you notice anything missing in the documentation, please feel free to open a new issue for that :)
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by