Describe the bug
The FilesProcessor has a problem with cropped images that have a autogenerate configuration that comes with a factor. (In case the original image is not that big).
To Reproduce
Steps to reproduce the behavior:
- Have a CE with an 100x100 image, apply a 75x25 cropping to it via the cropping editor in BE
- Have a processingConfiguration like
processingConfiguration.autogenerate.big.factor = 2
- The regular image is 75x25, the big variant is not 150x50, but 75x25 stretched to 100x100.
Expected behavior
Both target images should have same crop area, but different size. Maybe same size, but definitely no stretching!
Suspected problem
Comparing with the dimensions of the uncropped original is not correct for cropped images.
// multiply width/height by factor,
// but don't stretch image beyond its original dimensions!
'width' => min($targetWidth * $factor, $originalWidth),
'height' => min($targetHeight * $factor, $originalHeight),
Screenshots
Original:
Regular crop:
Stretched crop:
TYPO3 version and TYPO3 Headless version
- TYPO3 12.4
- EXT:headless 4.6.0
Describe the bug
The
FilesProcessorhas a problem with cropped images that have aautogenerateconfiguration that comes with afactor. (In case the original image is not that big).To Reproduce
Steps to reproduce the behavior:
processingConfiguration.autogenerate.big.factor = 2Expected behavior
Both target images should have same crop area, but different size. Maybe same size, but definitely no stretching!
Suspected problem
Comparing with the dimensions of the uncropped original is not correct for cropped images.
Screenshots
Original:
Regular crop:
Stretched crop:
TYPO3 version and TYPO3 Headless version