Problem image size

Hi @remcotolsma,

I have carefully reviewed the reported issue and tried to recreate it on my end. However, when an image with size 640×360 pixels is uploaded, the crop image size -600×360 was created successfully and it is fully accessible.

The issue most probably is caused by the theme your site is using. Could you please provide us with the exact URL you are experiencing the issue with so we can try investigating the case further?

Thanks for your response, it’s not related to the theme. I have setup a test / demo environment.

URL: https://remcot12.sg-host.com/
WordPress: 5.9.3
Theme: Twenty Twenty-Two

Plugins:

• Regenerate Thumbnails
• SiteGround Optimizer
• SiteGround Optimizer topic 15615072

The “SiteGround Optimizer topic 15615072” plugin contains the following code:

<?php
/**
 * Plugin Name: SiteGround Optimizer topic 15615072
 */

 add_action( 'after_setup_theme', function() {
	add_image_size( 'square', 600, 600, true );
	add_image_size( 'featured', 600, 400, true );
} );

See attachment:
https://remcot12.sg-host.com/klepperwei-mei-2022-9-2/

Corrupt image:
https://remcot12.sg-host.com/wp-content/uploads/2022/05/Klepperwei-mei-2022-9-600×360.jpg

Other resize image:
https://remcot12.sg-host.com/wp-content/uploads/2022/05/Klepperwei-mei-2022-9-150×150.jpg

Please note the following settings “WordPress admin dashboard” → “SG Optimizer” → “Media”:

Image compression level is Low (25%)

Original images backups are Disabled

If you need access to the test / demo environment you can reach me via [email protected].

Hello @remcotolsma

The issue is caused by the custom add_image_size parameter that is overwritten when the image compression is applied by the SG Optimizer. This happens only when the image that you upload is with the same pixels – 640×360 and the extension is .jpg. If the image dimensions are different the resized image doesn’t get corrupted.

There are a few possible alternatives in such a scenario:

— You may modify the add_image_size parameter within your template to a lower value(under x360) which will not cause the image to be overwritten and corrupted.

— You may enable the “Back up all original images” option from the Image compression tab in SG Optimizer. The sequence happens in a different manner which allows the image to be resized successfully without getting corrupted.

Best regards,
Georgi Ganchev

Is it not possible to solve the problem in the SiteGround Optimizer plugin? If not, can you explain why not? In which filter / action is the problem?

Hello Remco,

The issue is caused because your theme is adding to the site a custom image size of 640×360. This is hen overwritten when the image compression is enabled.

You may choose to disable the Image Compression setting in he Optimizer Plugin to prevent the corruption of this custom image size.

Regards,
Plamen.M
Tech Support Team
SiteGround.com

Do you fully understand the problem? If we disable the SiteGround Optimizer plugin there is no problem. So the issue is not caused by our theme, but by the SiteGround Optimizer plugin. Therefore, I hope you are willing to further investigate and resolve this issue. It cannot be the intention that SiteGround users upload an image and certain image sizes get broken.

Hello @remcotolsma

Our developers will check the case further and decide if there is something we can do to prevent image corruption.

Please be advised that the plugin works without any issues if there is no custom resolution change applied through the code that you provided us with. In addition, the case is observed only when the image that you upload is with this particular resolution of 600×360 and with a .jpg extension. If the image is with a .jpeg extension the problem doesn’t come up.

Best regards,
Georgi Ganchev

Hello @remcotolsma,

Our developers are currently working on a fix which should be included in one of the future releases of the plugin. While we cannot provide an ETA, we will update the topic, when the fix is released.

With that in mind, we will be marking this topic as Resolved.

You will still be able to post a reply, if needed.

Best Regards,
Gergana Petrova

Hello @remcotolsma,

A fix for the reported issue has been deployed and is available since version 7.1.3, most recent version is 7.1.4. Please update the plugin to the latest version and test on your end as well.

Best Regards,
Gergana Petrova

Just tested this, seems to be resolved indeed, thanks for your efforts.