TYPO3 Core

Ah sorry for the typos - I thought it was possible to re-edit a post now, but the button seems to be gone again - or was never there

I have experienced another use case for this, with TYPO3 6.2, which is simpler and probably more common:

• Editors keep an image archive in a non-public file storage (outside the root or protected by .htaccess) so that only used images will be accessible publicly.

• But if the image isn't resized, TYPO3 will use the original link, e.g. private/image-archive/image.png

• As this storage isn't public - the image won't be displayed!

dirty/slow workaround: rotate the image, so it needs to be re-processed

file {
...
params = -rotate 360
}

http://docs.typo3.org/typo3cms/TyposcriptReference/Functions/Imgresource/

This is an issue for me also.

I use Dropbox as the default storage, because I want to store a lot of original images.

However, the Dropbox FAL driver is slow to process images, so I always want to serve the image from the processed folder, located in fileadmin.

Currently in the news ext, my images are simply not served, if they haven't been processed, due to a bug serving a wrong URL from fileadmin.

But please include this in 6.2 if possible, don't wait until 7.

UPDATE - after spending hours looking for a clean solution:
I gave up on the clean solution, for anyone looking for a dirty solution, I ended up Xclass'ing the Extbase ImageService, following Stefans suggestion above:

class ImageService extends \TYPO3\CMS\Extbase\Service\ImageService {
    /**
     * Does exactly the same as the class it extends EXCEPT it ALWAYS creates a file
     *
     * @param File|FileReference $image
     * @param array $processingInstructions
     * @return ProcessedFile
     * @api
     */
    public function applyProcessingInstructions($image, $processingInstructions) {
        $processingInstructions['additionalParameters'] = '-rotate 360';
        return parent::applyProcessingInstructions($image, $processingInstructions);
    }
}

Remember to namespace the class and add something like this in ext_localconf.php:

$GLOBALS['TYPO3_CONF_VARS']['SYS']['Objects']['TYPO3\\CMS\\Extbase\\Service\\ImageService'] = array(
 'className' => 'YourVendorname\\Extensionkey\\Utility\\ImageService'
);

A very ugly solution, but it works, now all my images rendered with f:image, ends up in the processed folder.

Another use case we are just working around with the hack from Stefan (thanks!): AdBlock Plus may block images having certain words in their path, despite the images not being ads at all and thus should not be blocked. Having a processed file is a remedy for this problem, as the file- and folder name is changed.

Watch out if you use animated gifs, which will break if you're not excluding them.