Feature #59067
openAlways render image in temp directory
0%
Description
When rendering an image, TYPO3 6.x places it in the processed temp folder, where all temporary files are stored.
UNLESS the desired rendering size is equal to the file's original size. Then it will link to the original source file instead. This sounds economical and performance-conscious, but in some cases, this is not desirable.
I first posted this on Stackoverflow , where I learned that it's probably the ImageViewHelper who's designed to "Resize a given image (if required) and render the respective img tag".
My suggestion would be that, also for the sake of consistency, ImageViewHelper (if it's really the one who does it) would always place the used image in the processed folder. Even when it's not been rendered.
A use case:
I have all source images in a protected directory where access is handled by naw_securedownloads. So the img tag becomes something like this:
<img src="http://www.example.com/index.php?eID=tx_nawsecuredl&u=0&g=0&t=1399912827&hash=0a111ac62d806a0ff26649b065f03be674e7d9b3&file=fileadmin/private/images/example.png" />
Which then necomes performance issue, as the image won't be compressed nor cached properly, it seems.
So the performance-friendly idea of only creating a copy of the image when necessary works the other way.
Another use case:
Maybe simply don't want the original directories where the images are stored to appear in the frontend. E.g. if editors make deep nested directory structures or use some wording not ideal for public (e.g. something like /photos/photos/myphotos/uglytemporaryphotos/, you know how it goes).