Issue Bug Closed

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

Helmut Hummel 09/27/18, 11:02 updated 10/02/18, 10:28

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

Reviews 0

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