Issue Bug Closed

#80964[Install too] Combining images creates typo3temp into wrong location

Elmar Hinz 04/22/17, 17:54 updated 04/22/17, 18:40

Description

Combining images creates typo3temp into sysext/install/Start/

Issue

Test setup > Combining Images
Test setup > GDlib

Both tests write into typo3/sysext/install/Start/typo3temp/assets/ instead of typo3temp.

Then they fail, with the error message to be unable to read files from typo3temp.

 imagegif(typo3temp/var/transient/23def8d29aa3e1d849312dcc57e64ff8_maskNT.gif): failed to open stream: No such file or directory in /var/www/html/typo3_src/typo3/sysext/core/Classes/Imaging/GraphicalFunctions.php line 2818

 TYPO3\CMS\Core\Error\ErrorHandler::handleError(2, "imagegif(typo3temp/var/transient/23def8d29aa3e1d84…: failed to open stream: No such file or directory", "/var/www/html/typo3_src/typo3/sysext/core/Classes/Imaging/GraphicalFunctions.php", 2818, array)
12 imagegif(resource, "typo3temp/var/transient/23def8d29aa3e1d849312dcc57e64ff8_maskNT.gif")

Environment

TYPO3 v8.7.1

I don’t want to describe the full setup of the environment with a docker container, mounts and symlinks. In case you find the full description here:

https://hub.docker.com/r/elmarhinz/typo3.docker-development/

(Container elmarhinz/typo3.docker-development:v8.b)

Analyses

The tests of the other images work. Just the given two tests fail. They fail in a write step, while the read step of the created transient files is searching them in the right position.

I suspect the write step doesn’t resolve the base of the typo3temp in the same way as the other parts of the script do and fails under my special setup.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.