• Resolved Gal Baras

    (@galbaras)


    After configuring the plugin with Max Width = 2560 and Max Height = 1707, I ran a manual bulk optimisation. The output contained several times the message “Resize not required, image smaller than 1920w x 1920h”.

    These sizes don’t match the plugin configuration, so I checked a few of the original images, and they weren’t 1920×1920. Two were 1280×1919 and one was 1920×1372.

    I then checked an image that didn’t have that message, and it was 2560×1707, which is good. So where is the 1920×1920 coming from?

    Also, the message appeared for every thumbnail size, which makes no sense, because they weren’t supposed to be resized anyway, only optimised.

    Finally, the phrase “Previously Optimised” appears for many images. Does this just mean that the plugin “remembers” the image, but noticed it’s been recreated/changed?

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support adamewww

    (@adamewww)

    Hi Gal,

    I think this is probably something better looked at in detail via our support: https://ewww.io/contact-us/

    Can you send over the System info with your ticket, please?

    Additionally, if you would like to save a step, it may help to get a debug of one of the image that isn’t being resized properly. You can do this by:
    1. Enabling Debugging in the Support tab
    2. Clearing the existing log with the ‘Clear Log’ link
    3. Either deleting and reuploading that image or go to the media library, check the checkbox next to the image and going to the Bulk Optimize option in the dropdown at the top.
    4. Run the bulk optimizer on that image, you may need to check the ‘Force Re-optimize” option in the top right.
    5. Go back to the Support tab of the plugin settings and hit download log. Uncheck Debugging
    6. Send the debug log over to support attached to an email.

    Thread Starter Gal Baras

    (@galbaras)

    I think I’ve found the problem. Looking through wp_options, I saw this:

    ewww_image_optimizer_maxotherwidth = 1920
    ewww_image_optimizer_maxotherheight = 1920

    They match the bulk optimizer code and may cause images not to be resized.

    However, I don’t see these anywhere in the plugin’s settings within WordPress, so it seems like the only way to reset them is in the database.

    Also, it seems that the plugin checks ewww_image_optimizer_maxmediawidth and ewww_image_optimizer_maxmediaheight, which are the options settable in WordPress, only if ewww_image_optimizer_maxotherwidth and ewww_image_optimizer_maxotherheight aren’t set, which seems to be incorrect.

    For now, I’ve deleted the two options to prevent any future conflicts, but I have a feeling that I’ve made some images too small. Hopefully, I won’t have to restore them and resize again.

    Please advise quickly.

    Plugin Author nosilver4u

    (@nosilver4u)

    Hi Gal,
    The ewww_image_optimizer_maxotherwidth and ewww_image_optimizer_maxotherheight are holdovers from when we had those in the UI. They originally defaulted to 0, but when they were removed from the UI, the plugin didn’t “unset” them for folks that already had them configured.

    As you figured out, they can be removed/changed directly in wp_options. Originally, I believe they were listed in the overrides (constants): https://docs.ewww.io/article/40-override-options
    But it’s been so long, I must have removed them at some point, though they would still work as overrides.

    As to what the options are supposed to do, they were listed as applying to “indirect” media uploads–had to go look at an old video, since that was so long ago! In other words, they applied to resizing done everywhere except during a new upload to the media library or the post/page editor.

    Thus they apply to bulk optimization, and if configured, take precedence over the ewww_image_optimizer_maxmediawidth and ewww_image_optimizer_maxmediaheight as you saw in the ewww_image_optimizer_should_resize() function.

    Unless you checked Force Re-optimize, only images that had not been processed before would have been affected by the lower dimensions.

    The resize status is a false positive on the thumbs, it wouldn’t ever apply to them. But I can see that the status isn’t being reset in the right spot, so we get the status from the full-size version carrying over into the results for the thumbs.

    Hope that all makes sense, if you need further help, please send the system info via email as Adam mentioned.

    Thread Starter Gal Baras

    (@galbaras)

    Thanks for this. It makes sense, except…

    When setting new resize dimensions in the plugin, it might be time to remove the old settings, because the site admin clearly wants something else now.

    In case I’m missing something, at least warn the admin of this situation, so they can make an informed decision and take corrective action, if required. This is particularly important if the “other” dimensions are smaller than the respective new plugin setting.

    I was completely surprised by a SMALLER size being in effect, and now, I have images that are smaller than what I need.

    I’m guessing the originals are gone for good now, and if I want to do another round, I’d had to restore them from backup, right?

    Plugin Author nosilver4u

    (@nosilver4u)

    If you’re using the API on that site, it’s possible you can retrieve the originals for those images using the Restore Original option in Media->List mode.
    Otherwise, just restoring the images from a backup right before you ran the bulk process would be the next best route.

    I like the idea of clearing those legacy settings if someone sets new dimensions though, I’ll see what I can come up with on that.
    Should even be able to expose the old/legacy settings in a read-only capacity for those that have them set.

    Thread Starter Gal Baras

    (@galbaras)

    Love your work 🙂

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Strange resize output’ is closed to new replies.