Bug #86399
closedWrong processed folder resolved, when folder is configured to be on a different storage
100%
Description
During generation of processed files, a wrong processed folder is returned.
Szenario¶
Given the following storage configurations:
Storage 1: processed folder "foo"
Storage 2: processed folder "1:/bar"
Observation 1¶
When an image of Storage 2 is processed
I expect subfolders are generated in "1:/bar"
What happens is that subfolders are generated for "1:/foo" as well as for "1:/bar".
Observation 2¶
When an image of Storage 2 is processed, sys_file_processedfile record does not exist, but the file exists in "1:/bar/a/b/"
I expect the file not to be regenerated
What happens is that the file is regenerated, because it is looked for in "1:/foo/a/b/" first
Updated by Gerrit Code Review about 6 years ago
- Status changed from New to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/58410
Updated by Gerrit Code Review about 6 years ago
Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/58410
Updated by Gerrit Code Review about 6 years ago
Patch set 1 for branch TYPO3_8-7 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/58452
Updated by Helmut Hummel about 6 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 9bb994f492e75efcfe139c3d6a64ef42dbef9bd1.
Updated by Susanne Moog over 5 years ago
- Related to Bug #66209: ProcessedFile::setName checks existence for new objects added
Updated by Benni Mack about 1 year ago
- Related to Bug #89004: Image processing (on scaling) runs repeatedly for the same image on every page load added