Needs review
Project:
Image Optimize
Version:
8.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
15 May 2020 at 16:06 UTC
Updated:
15 Oct 2021 at 13:25 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
cosolom commentedComment #3
steven jones commentedThanks very much for your contribution! It is much appreciated.
Yeah, separate module I reckon, although I get that you'd probably want to extend the pipeline entity rather than provide a simple processor.
Marking as postponed while we work out what to do with this.
Comment #4
cosolom commentedWe can't use a processor because it has only an image url. And we can't determine a source for this image.
Comment #5
cosolom commentedThis patch preserve more informatin. And I hope that we can set the status "Needs work" so as not to lose sight of this task.
Comment #6
chrischaplow commentedThis is a very useful project. Photographers are particularly interested to preserve Meta Data especially IPTC and Copyright info and status of images on the web. Whilst there is no clear evidence that Search Engines currently use Meta Data there is much debate in SEO circles about it.
Comment #7
jcisio commentedI haven't tested yet but I like the approach. However I don't think Magick should be a requirement, it's only optional, so I remove composer.json from the patch.
Another question is, would it work with WebP module? I don't think so, unless we patch that module, too.