Bug #94609

Moving a file to a different storage will not invalidate or modify the processed entry

Added by Sybille Peters 10 months ago. Updated 7 months ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
File Abstraction Layer (FAL)
Target version:
-
Start date:
2021-07-21
Due date:
% Done:

0%

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

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.


Related issues

Related to TYPO3 Core - Task #77988: Moving folders between local file storages does not workAccepted2016-09-18

Actions
#1

Updated by Sybille Peters 10 months ago

  • Related to Task #77988: Moving folders between local file storages does not work added
#2

Updated by Sybille Peters 7 months ago

Can still reproduce this in 11 master but I am not sure if it is much of a problem since it does not really break anything.

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

Also available in: Atom PDF