Project

General

Profile

Actions

Bug #34160

closed

Replacing/Overwriting a file could leave a stale index record

Added by Andreas Wolf over 12 years ago. Updated about 10 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
File Abstraction Layer (FAL)
Target version:
-
Start date:
2012-02-21
Due date:
% Done:

0%

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

Description

Currently, when overwriting a file, we have this situation:

  1. When copying a file over another file, everything is fine
  2. When moving a file over another file, everything is fine if only one of them (or none) is indexed
  3. When the new file is freshly uploaded, everything is fine

So there basically is one critical case: When two index records would point to the same location after changing them (this already fails in the indexer when detecting files moved outside of TYPO3). Currently there is no logic to resolve such conflicts, but we should definitely have it.

In general, the simplest approach would be to take the most recently updated index entry and change the references to all other conflicting files to point to this uid. However, the infrastructure for these operations is still missing (e.g. in the repository)


Related issues 1 (0 open1 closed)

Blocks TYPO3 Core - Bug #45110: File is listed twice in sys_fileClosed2013-02-03

Actions
Actions

Also available in: Atom PDF