Wrong processed folder resolved, when folder is configured to be on a different storage
During generation of processed files, a wrong processed folder is returned.
Given the following storage configurations:
Storage 1: processed folder "foo"
Storage 2: processed folder "1:/bar"
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".
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