Bug #96922
openFAL file DuplicationBehavior::REPLACE is using public file path
0%
Description
When a file is uploaded with an existing name there are different behaviors to choose from.
One is the DuplicationBehavior::REPLACE which should replace the existing file.
Currently the "public path" of the file is used to get the file on the storage which does not make sense and fails, if the public path is returning something else then it is on the storage.
The public path must not be used to do file operations on the storage but only to provide a path for the public (web) usage.
Files
Updated by Sascha Egerer over 2 years ago
- Related to Bug #98005: Use sanitized filename as source identifier when replacing an image added
Updated by Simon Schaufelberger over 2 years ago
Currently the "public path" of the file is used to get the file on the storage which does not make sense and fails, if the public path is returning something else then it is on the storage.
How can this be reproduced?
Updated by Sascha Egerer over 2 years ago
- File Bildschirmfoto 2022-08-05 um 21.21.49.png added
Updated by Sascha Egerer over 2 years ago
- File deleted (
Bildschirmfoto 2022-08-05 um 21.21.49.png)
Updated by Sascha Egerer over 2 years ago
Add a `baseUri` like `my-custom-uri-path/` in the File Storage record.