#93129Crop an image from a storage not inside TYPO3s folder fails
Description
We use a storage that is outside of the TYPO3 folder.
All uses of the files from this folder work perfectly: frontend, in all image view helpers, filelist and so on.
Now an editor has noticed the following when cropping the picture:
No picture is loaded. See the screenshot:
The image cropping program calls the following URL which causes a 500 error: /index.php?eID=dumpFile&t=f&f=50287&token=8a6fe7ef5f5d8492810a5b623dd9ffe74f9cf70e
The following error appears in the error log: See screenshot:
For deployment reasons we cannot move the folder to the TYPO3 folder.
What I’ve tried so far:
The path set relatively: the same error
The path set absolutely: the same error
Is this maybe related to: https://forge.typo3.org/issues/90330
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Files 3
History 10
-
Christian Stern changed attached screencapture-www-theaterkompass-de-ddev-site-index-php-1608496191277.png 12/20/20, 20:30
-
Christian Stern changed
screencapture-www-theaterkompass-de-ddev-site-index-php-1608496191277.png12/20/20, 20:30 -
Christian Stern changed attached index-php-1608496191277.png 12/20/20, 20:31
-
Christian Stern changed subject
Crop image from a storage not inside TYPO3s install folderCrop an image from a storage not inside TYPO3s folder fails 12/20/20, 20:32 -
Riccardo De Contardi changed category 01/17/21, 21:21
-
Katja Lutz commented 01/21/21, 15:20
-
Mathias Brodala changed description 01/29/21, 13:44
-
Katja Lutz commented 03/01/21, 21:42
Quick update from my side: in our case the error lay in our own, custom built extension which had a fatal flaw in its extTablesInclusion-PostProcessing hook.
-
Christian Stern commented 05/16/21, 21:50
It looks like with 10.4.15 this false behavior is resolved. I can not reproduce it anymore.
Can anyone else confirm, that images are loaded correctly from any storages?
-
Benni Mack commented and changed status
NewClosed 06/24/24, 09:46I checked this, looks good so I will close this issue.
I am encountering this as well :)