Possible WooCommerce Conflict

@smellcoffee @mdaan

A fix (https://github.com/woocommerce/woocommerce/pull/22818) has been merged into master and should be part of WooCommerce 3.6. This is the related issue: https://github.com/woocommerce/woocommerce/issues/21800

Meanwhile we recommend you to use the workaround explained above.

Hope this information helps.

@smellcoffee @mdaan

A fix (https://github.com/woocommerce/woocommerce/pull/22818) has been merged into master and should be part of WooCommerce 3.6. This is the related issue: https://github.com/woocommerce/woocommerce/issues/21800

Meanwhile we recommend you to use the workaround explained above.

Hope this information helps for now.

Hello,

I have gone ahead and done these changes recommended, that being adding these to functions.php:

add_filter( 'woocommerce_resize_images', '__return_false' );
add_filter( 'woocommerce_background_image_regeneration', '__return_false' );

But was wondering now that I have added these is it safe to leave on “Compress new images in the background”?

If so, when does it usually do this? Like, how long does it take after the upload to take affect?

Hi,

You can still leave on “Compress new images in the background” and it will start compress the image as soon as it is uploaded.

Great – thank you!

Has the issue been resolved in the latest release of woocommerce? I want to install your plugin now but was wondering if I still needed to add the code

I have the same question as others… has this issue been resolved in the latest version of WooCommerce?

I would like to add your plugin, and I can add the work-around code to my child theme’s functions.php file, but if it has been resolved I would like to avoid having “extra” code where it isn’t necessary.

Before I install and activate your great little plugin, can you please confirm what actions I should take one way or the other?

TIA!

• This reply was modified 5 years, 6 months ago by richsadams.

Hi!

Sorry for the lack of recent updates.

I have just tested scenario’s that caused older WooCommerce versions to keep regenerating thumbnails when small product images were used. In the latest WooCommerce version (currently 3.7) I’m no longer able to reproduce the issue.

I haven’t tested all possible combinations of image sizes, so please let us know if you’re still experiencing issues while using WooCommerce 3.7 or newer in combination with this plugin.

@tinypng thanks very much for the fast response and will do!

I just wanted to add that it doesn’t appear to be resolved – I’m currently developing a site with the latest versions of your plugin (3.2.1) and WooCommerce (3.9.2), and find that the homepage takes ~25 seconds to load, with hundreds of HTTP calls according to Query Monitor, unless I add in your workaround, in which case it drops to around half a second (with no HTTP calls reported in Query Monitor).

Testing it on my local dev environment to rule out network issues, here’s my results:

Without your workaround:
Test 1: 27.07s
Test 2: 25.33s
Test 3: 24.91s
Test 4: 23.48s
Test 5: 25.86s

With your workaround:
Test 1: 0.49s
Test 2: 0.35s
Test 3: 0.40s
Test 4: 0.32s
Test 5: 0.48s

This is on a medium-large store (~1200 products, or ~15,000 if you include variations).

• This reply was modified 5 years ago by hughiew.

Hi Hughiew,

Thank you for brining this to our attention. We will see if we can run some tests with WooCommerce (3.9.2) and see if we can reproduce this issue.

Hi again @hughiew,

Could you please send us a message at [email protected]?

We need to request some additional information regarding your setup so a more direct line of communication would help speed things up. It would be very helpful if you could let us know which sizes the different images are (the original) of the page that you are running your test on.

@tinypng

Any updates regarding this. Am using WooCommerce Version 4.1.0 and was interested in using your plugin as I use your site all the time.

Hi @danielarteagawpinb

We actually never heard back from the previous user. If you have time to test it out then we would very much hear how it goes for you.

@hughiew We have written you a few times but haven’t heard back from you. Are you still experiencing issues?

Hi, is the code still needed for Woocommerce 4.2.2?