• Resolved Nicholas Griffin

    (@thetechnuttyuk)


    Hey,

    I noticed today that you updated the plugin to work with the Amazon Cloudfront plugin, which is great news, however this new functionality doesn’t seem to be working with the plugin we use for Cloudfront called AWS for WP (https://wordpress.org/plugins/aws-for-wp/).

    Well I say it doesn’t work, it does work for most image files like .jpg and .png but it isn’t working for webp, which is kinda of disappointing as this is a feature we would really like to use.

    We can see that the images are uploading to our server, but then they don’t seem to get picked up by the plugin and then make there way to AWS.

    If there’s some way you could get this working or even test it to see if there’s anything extra we need to do that would be great.

    Also I think this is a problem I need to take up with you guys, but if it isn’t please let me know and i’ll redirect myself to AWS for WP.

    Thanks,

    Nicholas Griffin

    https://wordpress.org/plugins/ewww-image-optimizer/

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author nosilver4u

    (@nosilver4u)

    It makes sense that the webp images would not get picked up by amazon, because there isn’t really any hook that would tell the AWS plugins (or any other plugins) that there is a webp image to upload. I’ll take a look at this along with pushing images to AWS during a bulk optimize.

    Plugin Author nosilver4u

    (@nosilver4u)

    You can follow this thread for progress updates on the AWS uploads: https://wordpress.org/support/topic/optimize-different-sizes?replies=20

    Plugin Author nosilver4u

    (@nosilver4u)

    Also want you to be aware that the included rewrite rules for apache will likely not work at all for images uploaded to AWS. You’ll need to see if there is any rewrite functionality on the AWS system (I’ll try poking around too on that issue, but no guarantee I’ll have time to do any thorough research).

    Plugin Author nosilver4u

    (@nosilver4u)

    Now that I’ve had some time to dig into this, I’m seeing that it is a substantially different issue than the other issue. That one was easily fixed by a quick call to the s3 uploader for that plugin. The webp issue will require some way to indicate to the AWS for WP plugin that a webp image is available. I think it will require adding an entry under ‘sizes’ in the attachment metadata, but have to think through the impact of doing that. In particular, I’m concerned what will happen when an image is edited in WP and the user tells WP to regenerate thumbs.

    Plugin Author nosilver4u

    (@nosilver4u)

    Ok, the uploading works, but figuring out the proxy setup is totally up to you. I think it is possible to use mod_proxy on your local server if you’re using apache. No matter how you implement this, it is going to involve some sort of http proxy setup, and that is totally out of my league.

    New code is in dev: https://downloads.wordpress.org/plugin/ewww-image-optimizer.zip

    Thread Starter Nicholas Griffin

    (@thetechnuttyuk)

    Hey,

    The new code seems to work perfectly, the only thing that doesn’t seem to work is it’s won’t upload WebP images when you re-optimize them, but that’s a tradeoff we are okay with as we weren’t going to bulk optimize all of our 7000+ images anyway xD.

    Thanks for working on that for us though. Am I right in thinking that this dev code will be in a public version when it is updated? Just checking before I update when it’s out.

    Plugin Author nosilver4u

    (@nosilver4u)

    Strange that the plugin doesn’t re-upload existing images, since the other Amazon S3 plugin does. I’ll double-check that when I have a chance, since there might be a way to trigger a refresh of the image. Even if you don’t plan to bulk optimize your existing library, plenty of other folks do, so it’s worth checking on to know for sure.

    And yes, this code is part of trunk, which will be rolled into production for the next release.

    Plugin Author nosilver4u

    (@nosilver4u)

    It might be worth noting that webp version don’t always get generated. If the webp version isn’t smaller than the original, then it gets discarded. In my testing, if a webp version gets generated on a re-optimize, then it does get uploaded to S3.

    When I did the same on a JPG that already had lossy JPG compression applied, the webp version was discarded. The JPG was already so small that webp resulted in no savings.

    Otherwise, things seem to be working as expected.

Viewing 8 replies - 1 through 8 (of 8 total)

The topic ‘WebP not uploading to Cloudfront with AWS’ is closed to new replies.