Project

General

Profile

Actions
Copy link

Bug #56727

closed

ExtractorRegistry can not handle Extractors with same ExecutionPriority

Added by Frans Saris over 10 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
File Abstraction Layer (FAL)
Target version:
-
Start date:
2014-03-10
Due date:
% Done:

100%

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

Description

The ExtractorRegistry::getExtractors() overrides existing instances with the same execution priority.

There is no check or notification about this. Further is could be that you have a extractor for Local driver and an extractor for a remote driver with the same execution priority, currently that is not possible.

I guess parts of https://review.typo3.org/#/c/27958/ could be used as basis for this change, also some test coverage would be nice.

Related issues 2 (0 open — 2 closed)

Related to TYPO3 Core - Bug #64942: Racecondition in Extractor Registry for Indexing FAL filesClosed2015-02-09

Actions
Related to TYPO3 Core - Bug #92643: Fix FAL meta data extraction prioritiesClosed2020-10-21

Actions
Actions
Copy link

Also available in: Atom PDF