TYPO3 Core

Oliver Hader wrote in #note-2:

How to reproduce this? Does it occur without ext:solr?

You can reproduce this bij setting up an indexer in TS for solr with a definition for a field to be indexed like this:

image_stringS = FILES
image_stringS {
references {
table = tx_extname_domain_model_project
fieldName = image
}
renderObj = IMG_RESOURCE
renderObj {
file.import.data = file:current:uid
file.treatIdAsReference = 1
file.width = 100
file.height = 100
}
}

Instead of a path to a rendered image, it will generate something like this in the index:
typo3/image/process?token=5be607cb4004796fcb1a7c4aaf83138fcaf44b20&id=544190

Can confirm this.

I wrote a scheduler task who sends fluid emails with images (f:uri.image). In TYPO3 11 the image path in these mails changed to something like typo3/image/process?token=5be607cb4004796fcb1a7c4aaf83138fcaf44b20&id=544190 and the images are not visible anymore.
With
unset($GLOBALS['TYPO3_CONF_VARS']['SYS']['fal']['processors']['DeferredBackendImageProcessor']);
I could fix the problem.