TYPO3 Core

Hi all,

File abstraction layer behaves odd for indexing and callbacks for extractors.

Using ext:extractor (but can be anything) cannot be run on scheduler task File Abstraction Layer: Extract metadata in storage (scheduler)

• ext:extractor installed and configured correctly; is called on file upload (working) as well should be called on above mentioned scheduler task
• jpg's with different meta-data in folder fileadmin/
• after upload, imageA has it's own metadata, as well imageB do so.
• after copying imageA onto imageB (via console, under the hood):
  - nothing changes in metadata of imageB, witch should show now metadata of imageA, even:
  - running File Abstraction Layer: Extract metadata in storage (scheduler)
  - running File Abstraction Layer: Update storage index (scheduler) at first and then File Abstraction Layer: Extract metadata in storage (scheduler)
  - setting "last_index" to 0 before running one or both tasks (as mentioned in http://meberhard.me/tag/scheduler/)
  - setting modified-timestamp to creation-timestamp as mentioned in https://github.com/xperseguers/t3ext-extractor/issues/26#issuecomment-667834446 does not work
  - deleting the sys_file_metadata in der database for these two files and rerunning all previous steps does not help:
  it creates again sys_file_metadata-entries, but empty.

I didn't find a way at all to reread metadata of files which are changed by an external script in meanwhile.

What i would expect is:
"Updates the Index/Cache Data of a Storage; only needed if changes to the storage are possible outside the backend (FTP, RemoteStorages)."
=> This is the original description of scheduler task Update storage index (scheduler) and it does not do it at all.
=> This is exactly what i'm searching for: Re-reading meta-data on existing files, which may have changed under the hood and are not modified by editors.

The whole behavior of the FAL-storage-indexer and extractor-callbacks seem to be very odd?

Thank you, Thomas