EWWW IO optimizes all sizes generated by WordPress.
What plugin are you using for the CDN? It should be running before they are uploaded, but it may not be. I can take a look if I know what plugin you are using.
I am using amazon s3 and cloudfront plugin and also amazon web services plugin.
I just installed the plugin and it is not uploading the compressed files to the CDN. While inserting the pictures it shows the compressed size and also points the url to the CDN but when i open the file the uncompressed file is showing up and its the same when inserting the photos.
Make sure you flush your browser’s cache, and please post a link to an example image, and let me know what the before and after sizes should be.
Just confirmed that Amazon S3 and Cloudfront is running with a higher priority level than EWWW IO. I’ll have to see if I can lower that safely, since it is a bit of a balancing act with other plugins to make sure we don’t run too soon, but running soon enough. In the meantime, you could request the developer of the Amazon S3 and Cloudfront plugin to bump up the priority on the wp_generate_attachment_metadata hook to something higher than 60.
The developer of the plugin is not responding to the messages in the support like 1 or 2 months, so no hope i think.
Meanwhile any modification on the EWWW plugin can make it work?
(I don’t know much about WordPress codebase)
I’m looking into it today. I had set it to 60 to run after the Image Store plugin, but that may not be necessary anymore. I need to do some testing, so I’ll let you know what I find out.
Discovered that the one plugin that was a blocker was doing some clever things that were unaccounted for. As a result, EWWW IO no longer needs to hook after that plugin, so I have changed the priority to run before the cloudfront plugin. 2.0.2 will be out early next week (or sooner).
Thanks for your great support. Will be waiting for the update. One more thing after the update if I bulk optimize the images will those be updated in CDN?
Nope, does the amazon s3 plugin have a bulk uploader?
UPDATE: just answered by own question from the plugin description: NO.
I’ll see if I can trigger an upload after a successful optimization, but that might not make it into 2.0.2.
The plugin description says it wont upload old images. But the images that are already uploaded also cannot be modified? i.e After optimization.
I guess all we can do is try it and see. Worst case, you would just need to delete your wordpress files from amazon’s servers, and THEN run the bulk optimization. You’ll be able to try it on a handful of images first before you try the full-blown bulk optimization. This function is definitely NOT going to be in 2.0.2 though. Because it would be a new feature, that will have to go in 2.1, but if you’re willing, I can give you the dev link once I have the function ready for testing.
Ok i will try it after you finish your coding. Mean while the 2.0.2 will work with the newly uploading images right.
it should, yes, please let me know right away if it doesn’t
Ok i will let you know as soon i test it.
