Feature #23636
closed
Enhanced TempFolder-Structure
Added by Heiko Nöthen about 14 years ago.
Updated over 9 years ago.
Description
We are using TYPO3 with the networkbased filesystem AFS (openafs.org). This FS only supports a maximum of 64000 files per directory - if alle filenames are 16 or fewer octets. If the filenames are longer the file consumes more nodes an so less files can be saved in the same directory.
Now my feature request: Is it possible to implement a temp system wich supports a more tree-based strukture? Lets make an example:
/typo3temp/pics/t/y/typo3.jpg
So we would have space for more then 43 million files.
The other part would be to reduce the length of the name to a minimum. Therefore it would also be great to give every temp file type an own directory. An example:
/typo3temp/tmb_8d02ebca9d.gif
My suggestion: /typo3temp/tmb/8/d/8d02ebca9d.gif
Greetings
Heiko Nöthen
(issue imported from #M15841)
Files
We also already had serious server crashes because of this problem, when gifbuilder has been used to intensive in some cases. So +1 for this useful feature request.
I have a workaround which address this issue.
It's just a few modification in t3lib_stdGraphic (currently working on TYPO3 4.7.7, will be obsolete in 6).
It consists in splitting the hash of the generated temporary filename into 2 subfolders.
I did not directly patched t3lib_stdGraphic, but I have XCLASSed tslib_gifbuidler (which is the final class used in the FE).
Maybe you can adapt the diff attached to fit your situation. The modified method is t3lib_stdGraphic::imageMagickConvert().
It would be nice to see this tiny modification reversed to the core.
- Description updated (diff)
- Status changed from New to Needs Feedback
- Assignee set to Mathias Schreiber
Hey guys,
is this still an issue with FAL?
- Status changed from Needs Feedback to Closed
- Assignee deleted (
Mathias Schreiber)
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.
Also available in: Atom
PDF