#21388typo3temp got filled with thousands of javascript_* files
Description
If you use “GMENU_LAYERS / TMENU_LAYERS” without a specific “layer_menu_id” then your typo3temp will be filled continously with javascript_* files.
TSref:
layer_menu_id
string
If you want to specifically name a menu on a page. Probably you don’t need that!
This is wrong, you SHOULD set it to avoid this bug if it’s not fixed.
The unique filename is created with a string md5(microtime()).
(Actually it’s intended to be unique.)
md5(microtime()) can create millions of different filenames causing typo3temp to be filled more and more.
Problems with temporary files with unique filenames are also mentioned in Bug #21387 (http://bugs.typo3.org/view.php?id=12375).
This bug can also show DoS-like behaviour.
The applied patch is a dirty bugfix. It replaces microtime() with a string built around env var TYPO3_HOST_ONLY.
A better fix should use a system wide (system=TYPO3) class-function especially written for purposes like this.
(issue imported from #M12376)
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Related issues 9
- Bug #20329cache_hash fills up with huge amounts of MENUDATA
- Bug #21387typo3tempgot filled with thousands of EXTERNAL_URL* files
- Bug #22311another Bug causing typo3temp to fill up with files
- Bug #23866layered menus generate "too much recursion javascript-error"
- Bug #23867Menu_Layers is screened incorrect
- Bug #23957nested XMENU_LAYERS and the typo3temp *.js caching bug
- Bug #24367changes in tmenu_layers.php broke TMENU
- Bug #28640TMENU_LAYERS does not always create unique IDs for the third level
- Task #46358Separate ext:statictemplates code from core