TYPO3 Core

Actually that seems to be a regression from #75880 - prior to that crop was handled as string and then became the Area object.

• LocalCropScaleMaskHelper::process gets the configuration array having ['crop' => Area(...)]
• it performs a json_decode(Area::__toString) in order to retrieve the properties
• issue #91571 revealed this design flaw by disallowing arbitrary classes during deserialization

Oliver Hader wrote:

Actually that seems to be a regression from #75880 - prior to that crop was handled as string and then became the Area object.

I agree. We can fix the initial regression and json_encode the crop property before serializing the configuration.
That actually was my first approach when working on a fix. However this would invalidate all processed files,
because the configuration hash would change.

BackendUtility::getThumbnailUrl (expects JSON) via ThumbnailViewHelper and does not pass crop information at all, since it's given as Area object. This would be another candidate when switching to plain JSON for passing the cropping information...

Patch set 1 for branch 10.4 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/64913

Patch set 1 for branch 9.5 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/64914