Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backend module dashboard crashes on multi-instance application #578

Open
2 tasks done
RinyVT opened this issue Jul 17, 2024 · 0 comments
Open
2 tasks done

Backend module dashboard crashes on multi-instance application #578

RinyVT opened this issue Jul 17, 2024 · 0 comments

Comments

@RinyVT
Copy link
Collaborator

RinyVT commented Jul 17, 2024

  • I've read and understood the contribution guidelines.
  • 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?

  1. Setup TYPO3 in a multi-instance setup
  2. 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)

Technical info

  • TYPO3 version: 10-11-12
  • Yoast SEO version: 9
  • Relevant extensions in case of a bug: -
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant