Issue Bug Closed

#105985typo3/cms-filemetadata doesn't import fields correctly on Apache Webserver

m s 01/23/25, 18:57 updated 01/23/25, 20:28

Description

Meta data from files are not imported into the correct metadata fields in TYPO3 when using Apache. However, it works under nginx.

Attached is a licence-free example image. If I upload this under nginx, the title is filled in correctly in TYPO3’s meta data field.
If I upload the same image under Apache, the title field remains empty.

Another example: For images with keywords in the meta data, the keywords are copied into the keyword field AND the description field, although the description is also stored in the image. Again, it only does not work on an Apache web server.

I am using the latest version of TYPO3 12: 12.4.26

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

Files 1

History 3

  1. Garvin Hicking commented and changed status New Needs Feedback 01/23/25, 19:40

    Hi m,

    that sounds a bit odd – the EXT:filemetadata extension is only there to provide database fields. It does not auto-populate data when uploading files. For that other extensions like https://extensions.typo3.org/extension/extractor would be used.

    Also, using Apache or Nginx should not really affect this. How exactly do you switch this environment? Could it be that also different PHP configuration is used in that case, that sounds like a more probable culprit for your issue…?

    Maybe you can provide more details.

  2. m s commented 01/23/25, 19:48

    Hi Garvin,

    thanks for your fast reply!
    And yes, it could be that the extractor extension is the problem. This is also installed in my installation. Thanks for hint!

    We have an Apache Live server with the problem and a local DDEV environment with the problem when also running as an Apache server. Switching to nginx on DDEV “solves” the problem.

    I will create an issue for the extractor extension!

  3. Garvin Hicking commented and changed status Needs Feedback Closed 01/23/25, 20:28

    Alright I’m closing this with your feedback, thanks for the quick response!

    This will VERY likely be related to ddev having the needed conversion/extraction libraries, and your lifeserver not.

    Ddev comes with many existing tools that production hosting environments do not have by default. Check out theye requirements and try to install the tools on your production environment.

    Good luck!