Feature #70858: Add possibility to "hook" into the processing chain - TYPO3 Core - TYPO3 Forge

Custom queries

12 LTS
Accessibility
Dashboard issues
Easy tasks
Extbase Issues
FAL Issues
FAL Sprint 2023
Hierarchical Issues
Issues reported for v11
JavaScript issues
JavaScript Issues (w/o Epics/Stories)
Most wanted Bugfixes
Most wanted Features
My open issues
New & Unassigned
No feedback within 90 days
Open Bugs
Open issues of 10
Page Tree Regressions after 2020-07-28
Recently modified
Regressions
Stabilization Issues
Usability or UX

Watchers (3)

Benni Mack
Charles Coleman
Georg Ringer

Actions

Copy link

Feature #70858

closed

Add possibility to "hook" into the processing chain

Added by Frans Saris over 8 years ago. Updated 4 months ago.

Status:

Closed

Priority:

Should have

Assignee:

Category:

File Abstraction Layer (FAL)

Target version:

Start date:

2015-10-20

Due date:

% Done:

Estimated time:

PHP Version:

Tags:

Complexity:

Sprint Focus:

Description

It should be possible to hook into the processing chain so you can manipulate the result of processed files.

For instance to:

change the filename of the processed file
watermark all processed files

Related issues 2 (0 open — 2 closed)

Related to TYPO3 Core - Task #67754: Cleanup "crop" implementation

Closed

2015-06-25

Actions

Related to TYPO3 Core - Epic #88027: Properly handle Hooks/Signals and Events

Closed

Benni Mack

2022-04-22

Actions

Issue # Delay: days Cancel

History
Notes
Property changes

Actions

Copy link

Updated by Charles Coleman over 8 years ago

I wholeheartedly second this feature request. This is something that I could have use on several client sites yesterday.

Actions

Copy link

Updated by Riccardo De Contardi about 7 years ago

Target version changed from 8 LTS to 9.0

Actions

Copy link

Updated by Benni Mack over 6 years ago

Parent task deleted (~~#54229~~)

Actions

Copy link

Updated by Susanne Moog about 6 years ago

Target version deleted (~~9.0~~)

Actions

Copy link

Updated by Susanne Moog about 5 years ago

Basically this is already prepared, but the registry / evaluation part is missing. There is a `ProcessorInterface` which is currently only implemented by the `LocalImageProcessor` which is then directly used in `\TYPO3\CMS\Core\Resource\Service\FileProcessingService::process` - at that place there should be a chain of processors instead with configured task types and priorities.

Actions

Copy link