Project

General

Profile

Actions

Bug #86399

closed

Wrong processed folder resolved, when folder is configured to be on a different storage

Added by Helmut Hummel over 5 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
File Abstraction Layer (FAL)
Start date:
2018-09-27
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
8
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

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


Related issues 2 (1 open1 closed)

Related to TYPO3 Core - Bug #66209: ProcessedFile::setName checks existence for new objectsClosed2015-04-01

Actions
Related to TYPO3 Core - Bug #89004: Image processing (on scaling) runs repeatedly for the same image on every page loadNew2019-08-23

Actions
Actions

Also available in: Atom PDF