Epic #77810: Improve (responsive) image handling
Add image manipulation (crop) to filelist itself and edit original image
With TYPO3 7.6 you can crop an image in sys_file_reference (e.g. in a content element), but you can not crop the image directly in the module file list. This would be a very useful feature.
Add a ImageManipulation field to sys_file and use this as default value in sys_file_reference
Updated by Sascha Egerer over 6 years ago
My comment from Gerrit:
Just tried to rework this patch at the coding night but stumbled over multiple problems. I can remember that some of these problems where the main reason i stopped here.
There are some conceptional problems with this feature.
1. The file relation does always have the cropping information in the database which means that the cropping information from the file metadata is always overridden. Thats a thing that we may get fixed somehow.
2. The cropVariants can be overridden on a per field basis. That means that the cropVariants could be different on a field then the default ones defined for the file. Each crop variant can have multiple allowed aspect rartios. It is very hard to merge those settings and just allow the crop variants defined in the file if the are allowed by the configuration of the per field configuration.
Antoher idea could be to save the cropping information not in the relation and not in the file but in a seperate "cropping" table.
The cropping variants (sets) can be configured with a name. Than those croppings a created for a named set and saved in the cropping table.
On a per field basis you can then allow which cropping set you allow and not define the crop variants.
Then you have also the possibility to define the cropping in the file and they a "selectedable" in the file relation.
But i will stop working on this patch for now as it is a really big change that should be rethinked from a conceptional point of view.
Updated by Christian Kuhn about 2 years ago
- Status changed from New to Closed
Hey. I'm going to close this feature request for now since a PoC implementation failed due to various conceptual issues (for instance that cropping is usually bound to the consuming element).
This issue could be picked up again, but I'm unsure if the list module is actually the right place to do these things.