Hello. Image metadata can have property Orientation: http://sylvana.net/jpegcrop/exif_orientation.html
When EXT:extractor calculates width and height, it not take it into consideration and may save switched dimensions to database which may cause another issues, eg. be crop tool for those image is not working properly because rendered image have different dim ratio then from database.
Eg:



Crop results:
User input:

Typo3 saved it as:

My temporal solution is to override JSON configurations and remove width / height mapping in EXT:extractor but i'm not sure it's foolproof. Without those mappings, width/height is saved properly, at least testing image from example above. Another issue is i have dosen images on that Typo3 and don't know how to fix database according to files exif... Help.
More context about that issue: https://forge.typo3.org/issues/69274
Hello. Image metadata can have property Orientation: http://sylvana.net/jpegcrop/exif_orientation.html
When EXT:extractor calculates width and height, it not take it into consideration and may save switched dimensions to database which may cause another issues, eg. be crop tool for those image is not working properly because rendered image have different dim ratio then from database.
Eg:

Crop results:

User input:
Typo3 saved it as:
My temporal solution is to override JSON configurations and remove width / height mapping in EXT:extractor but i'm not sure it's foolproof. Without those mappings, width/height is saved properly, at least testing image from example above. Another issue is i have dosen images on that Typo3 and don't know how to fix database according to files exif... Help.
More context about that issue: https://forge.typo3.org/issues/69274