#98174Not processing images when indexing in Solr
Description
I have the image processing problem of #93133 in TYPO3 11.5.
When I unset the DeferredBackendImageProcessor with the line
unset($GLOBALS['TYPO3_CONF_VARS']['SYS']['fal']['processors']['DeferredBackendImageProcessor']);
everything works.
TYPO3: 11.5.14
PHP: 8.0.21
ext-solr: 11.5.0-rc-3
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Related issues 2
History 6
-
Oliver Hader changed Related to #93133 <span data-processor="relativetime" data-value="2022-08-22T07:13:19+00:00" > 08/22/22, 07:13 </span>
-
Oliver Hader commented and changed status
NewNeeds Feedback <span data-processor="relativetime" data-value="2022-08-22T07:14:26+00:00" > 08/22/22, 07:14 </span> -
Albert van der Veen commented <span data-processor="relativetime" data-value="2022-10-01T10:57:16+00:00" > 10/01/22, 10:57 </span>
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 -
Michael Sollmann commented <span data-processor="relativetime" data-value="2023-02-27T16:50:05+00:00" > 02/27/23, 16:50 </span>
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. -
Georg Ringer changed Related to #98684 <span data-processor="relativetime" data-value="2024-07-31T14:32:15+00:00" > 07/31/24, 14:32 </span>
-
Georg Ringer commented and changed status
Needs FeedbackClosed <span data-processor="relativetime" data-value="2026-10-02T07:39:33+00:00" > 10/02/26, 07:39 </span>The DeferredBackendImageProcessor only kicks in during a backend request.
Indexing or sending mails via the scheduler on CLI is not affected, as no
request exists there.If images are generated within a backend request for use outside of the
backend (e.g. “Index now” in the Solr module, or a scheduler task executed
from the backend module), deferred processing can be disabled for that call
instead of unsetting the processor globally:$context = GeneralUtility::makeInstance(Context::class); $context->setAspect('fileProcessing', new FileProcessingAspect(false));This is available since v11.0, so the behaviour is intended and should be
handled by the calling code (e.g. EXT:solr). I am closing this issue – feel
free to reopen if the problem persists with the aspect set.
How to reproduce this? Does it occur without ext:solr?