Product thumbnail size not editable after last update

Gallery thumbnails should be square and cropped. Once image regen completes they won’t appear squished.

https://github.com/woocommerce/woocommerce/wiki/Thumbnail-Image-Regeneration-in-3.3-

OK – so can you please tell me where we can set the cropped size of the gallery thumbnails (the main product image thumbnails)?

Customize > Product Images > Thumbnail Cropping, is just for the category thumbnails.

To explain further, previously I had set the single product page thumbnails (thumbnail size) to 128x70px. This was done via “Media Settings > Media”.

Now however, since the last WC update, the main product image thumbnails are all 100x100px and no longer how they were before.

I did stop the automatic thumbnail regeneration, and wonder if that is the problem? If I download the “Regenerate Thumbnails” plugin, is it possible to return all the “thumbnail sizes” to 128x70px, as they are set in the Media Settings?

Thanks

Apologies for a further post. I see in the “Regenerate Thumbnails” plugin that there are 2 registered thumbnail sizes which appear to be both used for the product image thumbnails (single product page):

“thumbnail” and “woocommerce_gallery_thumbnail”

Is that normal?

The cropped size is set as 100×100 and can be changed by the theme/with code. There is no UI for it.

> To explain further, previously I had set the single product page thumbnails (thumbnail size) to 128x70px. This was done via “Media Settings > Media”.

This size was never used in core. The WP thumbnail size is not used on any of our pages.

> I did stop the automatic thumbnail regeneration, and wonder if that is the problem? If I download the “Regenerate Thumbnails” plugin, is it possible to return all the “thumbnail sizes” to 128x70px, as they are set in the Media Settings?

Filter woocommerce_gallery_thumbnail_size and return ‘thumbnail’ then regen if thats what you need.

add_filter( 'woocommerce_gallery_thumbnail_size', 'custom_woocommerce_gallery_thumbnail_size' );

function custom_woocommerce_gallery_thumbnail_size() {
return 'thumbnail';
}

@mikejolley wc is great, but this change in image size is not good! It is not possible now to write the code to change the size of the thumbnail.

I did a test on the stangin website with wc 3.3.2 and the thumbnails of the new products are 100×100, when before they were 180×180 measure set in wordpress.

In addition to the fact that with WC 3.3.2 I find myself a new 768×768 immangina resimensions used as the main image, when in the wc settings I inserted 600×600 …..

Mike saw the large number of people who have problems with image sizes, can not you do something? and give us the opportunity to choose the measures.

thank you

• This reply was modified 6 years, 9 months ago by nick8182.
• This reply was modified 6 years, 9 months ago by nick8182.

Mike you sorted it with that filter. Thank you so much as I would never have got there without you.

Now I have that filter in place to use the WordPress “thumbnail”, can you tell me if I should disable the “background regeneration” too? Basically will the WC background regeneration interfere and create more images on our server which are not required?

Thumbs up and cheers

@ nick8182 – check the filter that Mike just gave me. It returns the main product image thumbnail sizes (single product page) to those set via WordPress core. You might have been using these, which are set via “Media Settings > Media”.

@dav74 thanks I tried the code but with the theme flatsome does not work, loaded a new image and the thumbnail is always 100×100, when in the media settings is 180×180.

But it is not possible that with each update of WC 3, there are these problems, the images are the easiest thing, but those of woocommerce are making it difficult.

@nick8182 I could really discuss these things with you for several hours over some beers ?? I get quite nervous when WooCommerce releases a bigger update, as it can equate to a lot of work to get things working again. I appreciate these guys are all hard at work trying to improve things, but you need to be careful when there are so many themes out there.

In a perfect world none of us would use third party themes, and we would restrict the number of active plugins to less than 15. However I have just over 35 active plugins, as that is the business model which WooCommerce is built on. When all works well I am happy, but it’s sadly a full time job.

My sites were a total mess visually after the WC 3.3.1 update (which unfortunately our hosting automatically updated for me in the middle of the night), and I had to scramble to revert all our sites to a previous saved version. The issue was predominantly theme related, and my theme provider thankfully brought out a fix within a couple days. So, no doubt many people are asking Flatsome the same thing as you right now, and hopefully they release an update soon ??

@dav74 Did you try to see if the changes worked with firefox? because inserting this code with CHROME the image thumbnail has the size of the main image set in woocommerce in my case 600×600 and does not take the thumbnail set in media.

@nick8182 No I have no issues between different browsers. Adding a filter like that should not be browser specific ie if it works on one browser, it should not be any different with another browser. The only thign which might be causing a difference between browsers is cache. Try deleting all your bowser cache.

@mikejolley

You may have missed my question with the various other posts. Firstly many thanks for the filter, as it sorted my problem.

Now I have that filter in place to use the WordPress “thumbnail”, can you tell me if I should disable the “background regeneration” too? Basically will the WC background regeneration interfere and create more images on our server which are not required?

Thumbs up and cheers

@dav74 I don’t think it should be disabled. Those images are only regenerated if needed based on settings. I would consider Jetpack Photon though – it negates the need for it and handles everything on the fly. You’ll see greater performance with it that way as it’s also a CDN.

@mikejolley OK thanks for the info. I had occassionally issues where the Cloudlare CDN service would stop images showing on the front-end, so bit wary of CDN services now. But thanks and might give it a test.