• Resolved hmbehrens1

    (@hmbehrens1)


    Per https://make.ww.wp.xz.cn/core/2019/10/09/introducing-handling-of-big-images-in-wordpress-5-3/ , when uploading a “big image”, a scaled down version is made with a -scaled suffix in the filename, which becomes the “main” image that’s linked in the Media Library, while the “Original Image” still remains in the file system, but not easy to find by the user in the admin, mainly linked to from the Edit panel of the file in the Library.

    When doing a Bulk Resize with Imsanity, the plugin resizes the new -scaled image file but leaves the Original Image intact. Thus negating much of the space-saving benefits of the plugin – it is no longer useful to correct when clients have uploaded huge images in the past.

    Is there any plan to update the Imsanity plugin to deal with resizing the Original Image of the images in the Media Library as well as the scaled-down image? Thank you.

    (Note that it does prevent a huge original image to be uploaded while the plugin is active – this is specifically about doing Bulk Resize to images already uploaded into the Media Library by the time the plugin is installed.)

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

    (@nosilver4u)

    I was not planning to alter the original version of the image for WP 5.3+ during a bulk resize.

    As you noted, for new uploads, this is not an issue, as Imsanity scales the image before WP touches it.

    Which makes me think, “hmm, that’s a bit inconsistent…” So perhaps a new option that leaves originals by default, but can be enabled to remove the originals during bulk operation? Or perhaps to scale the image using the original and THEN remove it? Not sure what to think there. Thoughts?

    Thread Starter hmbehrens1

    (@hmbehrens1)

    Well, here’s our situation: Since November 2019 one of our clients has been uploading raw photos, of 10-40 MB filesize each, to her site, her site’s uploads folder now sits at 3.8 GB which is far and away too large for her website (it is a simple real estate site with photos of model homes), and makes it unwieldy and difficult to back up.

    In the past, we have been able to use Imsanity to recover almost all of this wasted disk space, but leaving the “original images” as left behind by WP 5.3+ untouched means that we now recover almost none of it.

    And again, this is a case where the original images are useless, they are way too large to ever do anything with, they’re photos of 8000+ pixels on a side. Literal wasted disk space.

    It would restore a lot of usefulness into the plugin for us if we could have the option to simply delete the original images and stay with Imsanity’s resized image as the new “original image”, same as if the image were being uploaded new with Imsanity installed and resizing new uploads. With Imsanity installed, the original image never even makes it into the filesystem, only scaled down one does, so it would be the same behavior/final result like this.

    This is mostly just a feature suggestion as I can always go in and delete the originals by hand of course. Not really a “bug”.

    • This reply was modified 6 years, 1 month ago by hmbehrens1.
    Plugin Author nosilver4u

    (@nosilver4u)

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

The topic ‘Does not resize “Original Image”’ is closed to new replies.