[X] I've searched for any related issues and avoided creating a duplicate issue.
Please give us a description of what happened.
If you run an installation on multiple instances, for example with Kubernetes, and the temp folder is not shared it's possible that the Dashboard module crashes because it uses f:image with an extension path.
This causes to write the processed image to the temp folder instead of a storage.
When the file is written on pod 1 and then the Dashboard gets accessed on pod 2, the image does not exist and the module crashes.
How can we reproduce this behavior?
Setup TYPO3 in a multi-instance setup
Visit the Dashboard module on one instance and then on another instance
Additional context
This should be fixed by not using the f:image viewhelper but just a img tag where the image already has the correct dimensions (instead of resizing it with the f:image viewhelper)
Please give us a description of what happened.
If you run an installation on multiple instances, for example with Kubernetes, and the temp folder is not shared it's possible that the Dashboard module crashes because it uses
f:imagewith an extension path. This causes to write the processed image to the temp folder instead of a storage. When the file is written on pod 1 and then the Dashboard gets accessed on pod 2, the image does not exist and the module crashes.How can we reproduce this behavior?
Additional context
This should be fixed by not using the
f:imageviewhelper but just aimgtag where the image already has the correct dimensions (instead of resizing it with thef:imageviewhelper)Technical info