Bug #94609
open
Moving a file to a different storage will not invalidate or modify the processed entry
0%
Description
Even after flushing the page cache, the processed file is still loaded from the old location (e.g. fileadmin/_processed_/7/4/csm_file_f2a9dd6eb0.png). Ideally, when moving a file to a different storage, the processed file entries in DB table sys_file_processedfile should be removed or updated and the processed files itself should be removed or moved.
Tested with 10.4.18.
Updated by Sybille Peters over 3 years ago
- Related to Task #77988: Moving folders between local file storages does not work added
Updated by Sybille Peters about 3 years ago
Can still reproduce this in 11 master.
Even after moving the file to a diffent storage (e.g. f/ instead of fileadmin/) and flushing cache, the processed file is still loaded from the old location, e.g. fileadmin/_processed_/e/4/csm_file_17c9247468.png
Updated by Stefan Terborg over 1 year ago
- TYPO3 Version changed from 10 to 11
- PHP Version set to 7.4
I have a news record with a pdf file from storage S1. When I move the file to storage S2 the frontend still shows the old path. The file download leads to a 404. In the news record the file is marked as missing.
This should be fixed as the file relation seems to be broken.