Closed (works as designed)
Project:
Crop API
Version:
8.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
20 Apr 2018 at 02:45 UTC
Updated:
3 Jan 2020 at 15:34 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
firewaller commentedPatch attached.
Comment #3
Eitisha commented@ Patrick
The patch looks good and applied successfully .
Attached is the screenshot for applied patch.
Thanks
Comment #4
firewaller commentedComment #5
berdirWhat issues does this cause? And I don't think this is correct, adding a crop needs them to be re-created as well if they already exist?
Comment #6
firewaller commentedFlushing an image style on image insert is unnecessary since the image style does not exist yet for that image. It has been a while, but I remember this was causing issues for programmatically generated image styles and throws some sort of error or warning.
Comment #7
berdirI've never had a problem with that, nor do the tests. Maybe that only happens in combination with another module or so, we'll need backtrace of those errors to continue here.
Comment #8
firewaller commentedI forget the use-case where I was experiencing the issue. Regardless, isn't it a waste of resources to clear an image style instance on an insert? I can't think of a scenario where it would be of benefit.
Comment #9
berdirOnly the crop configuration is new, the image and its image styles could have been created a long time ago, there is no way for us to know if image styles have been created between creating the image and creating the crop. If you do bulk import/migration of images with crop configuration where you know that it is currently the case, then you can use the existing setting to disable it temporarily.
Comment #10
firewaller commentedMakes sense. In that case I misunderstood the functionality and we can ignore this with a custom workaround for the bulk generation. Thanks!