Forum Replies Created

Viewing 15 replies - 1 through 15 (of 196 total)
  • Plugin Author OriginalEXE

    (@originalexe)

    Hello,

    I am in the process of rewriting this plugin from scratch and will be releasing a new version soon. Hopefully, that will solve your problem.

    Plugin Author OriginalEXE

    (@originalexe)

    Hello Brittney,

    Apologies for ignoring you. I am in the process of rewriting this plugin from scratch and will be releasing the new version soon. Hopefully, that will fix your problems.

    Watch out for the new version 🙂

    Plugin Author OriginalEXE

    (@originalexe)

    Hello,

    Plugin will not remove those images since it has no way of detecting their request (it only detects images that are called using one of the WordPress internal functions for fetching attachments). The plugin never removes sizes that you can choose from when inserting an image inside the post, including ‘thumbnail’, ‘medium’ and ‘large’: https://github.com/OriginalEXE/Optimize-Images-Resizing/blob/master/inc/class-cli-command.php#L87
    I would still recommend creating a backup of your website just in case something goes wrong, you can never be too safe.

    Plugin Author OriginalEXE

    (@originalexe)

    Hello @dav74,

    I am glad you found the plugin useful. I will have some time this weekend to work on improving it (it has not been updated in a long time), and I will check the WooCommerce compatibility as well.

    Thanks for reporting this, will let you know what I find out.

    Plugin Author OriginalEXE

    (@originalexe)

    Hello,

    apologies for the late reply.

    That line checks whether the size already exists for the current image, looks like it for some reason reports that it does even though it’s not? What is the result, you get broken images on the frontend?

    Plugin Author OriginalEXE

    (@originalexe)

    Hello,

    apologies for missing your post, are you still experiencing this issue? If so, would you be able to provide me with error logs for your server?

    Plugin Author OriginalEXE

    (@originalexe)

    Awesome to hear, I am glad it works well for you!

    Plugin Author OriginalEXE

    (@originalexe)

    Hello, apologies for missing your question!

    The “need” is determined by code calling the internal WordPress functions that fetch the image in a specific size.

    For example, your WooCommerce theme on the frontend might have this:
    <?php the_post_thumbnail('shop_catalog'); ?>

    When a page that contains that code is requested, plugin will check if the image of that size already exists, and if not, do the resizing and serve the image.

    For the Elementor plugin, I can’t tell you precisely since I have never used it, but it depends how it handles the selection. Does it generate all URL’s before offering your selection (in which case it would generate all sizes at once losing the benefit of this plugin), or maybe it only saves the info about the image you need and then on the frontend it does the actual fetching of the image URL.

    As for the WooCommerce product images, they don’t get deleted, only their additional images. Then, if they are requested by plugins/themes (through the use of the functions as I mentioned above), they get regenerated.

    The benefit of this approach over the default WordPress way is that sizes are generated only when your code actually requests them, and not when the image is uploaded.

    • This reply was modified 2 years, 8 months ago by OriginalEXE.
    Plugin Author OriginalEXE

    (@originalexe)

    Hi,

    not sure what exactly you mean. The plugin doesn’t change how your images are delivered, you still get exactly the same sizes you would before activating the plugin, the only difference is that they are created when actually needed, and not on upload (exception being the default WordPress sizes as explained in the readme).

    Plugin Author OriginalEXE

    (@originalexe)

    Hello,

    that is a valid concern. Unfortunately there is no built in way to force the processing of the images. The problem is that in order to do that, you have to actually trigger a visit on all of your urls, since there is no programmatic way to determine which page will need which images sizes. You could do it by cloning your site to a staging area, activating the plugin and cleaning up, and then using some tool or script to trigger a visit on each of your post/page. Once that’s done, you restore it to the live site. Now that might be more complicated if you update your site with the new content very often, or if your visitors are content creators as well.

    As for the nginx compatibility, I have not tested it, but I don’t see a reason why it wouldn’t work. The plugin doesn’t rely on some clever url rewrites or something like that, it hooks into internal WP action that gets called each time the image is requested, and does the work there, so server setup should not matter.

    P.S. Regarding your concern, another thing you could do is activating the plugin and not cleaning up the existing media library, and only letting the plugin handle future uploads. The only problem is that your currently uploaded images won’t be cleaned up so you would only see benefits with your future uploads. Not really a solution to your problem but just thought it’s worth mentioning.

    Plugin Author OriginalEXE

    (@originalexe)

    Hello,

    thank you for reporting this. A bit busy at the moment but I will take a look at it this week and check if I can fix the compatibility with the said plugin.

    Just to be sure, you are talking about this plugin: https://wordpress.org/plugins/wp-retina-2x/ ?

    Plugin Author OriginalEXE

    (@originalexe)

    The plugin disables all sizes generation, and then only if WordPress requests one of them, it generates it that one time and it stays there. That way you are sure that you are only using the sizes you actually need.

    That said, default image sizes are not touched because those are used in the media gallery, so they would be re-generated anyway as soon as you visit it, causing unnecessary processing to happen, so this plugin help the most when your theme or plugins register their custom image sizes.

    I have not tested the compatibility with ewww but I imagine it should work fine since my plugin doesn’t do anything weird or hacky.

    Plugin Author OriginalEXE

    (@originalexe)

    Yes, correct, the size will stay the same, you will just have smaller number of actual files in your wp-content/uploads directory.

    And I don’t blame you, the plugin name is not the best 😛

    Plugin Author OriginalEXE

    (@originalexe)

    Hi,

    that’s actually a bug (kinda). When you click on it, you get a list of the files that were removed, but only if you checked the checkbox above to keep the log.

    I forgot to remove the link if the log is not being kept, will fix that in the next update.

    Thanks

    • This reply was modified 2 years, 11 months ago by OriginalEXE.
    Plugin Author OriginalEXE

    (@originalexe)

    Hi,

    the plugin works in the background and it should stay activated, you don’t need to run the cleanup manually anymore.

Viewing 15 replies - 1 through 15 (of 196 total)