cropping no longer possible after update – server error - page 2

Resolved mariachellini
(@mariachellini)

5 months ago

Just updated the plugin to the latest version 1.9.0

Unfortunately now it’s no longer possible to crop an image at all. After choosing the crop in the image when hitting the blue crop button (“Zuschnitt übernehmen”) a popup shows up with the message that there was an error connecting to the server (“Fehler beim Verbindungsaufbau zum Server.”)

Everything worked fine before the update, no server changes were made.

Hope this can be adressed quickly, so we can get back to using this great plugin.

Viewing 15 replies - 16 through 30 (of 31 total)

← 1 2 3 →

alexgwcog
(@alexgwcog)

5 months ago
Hi @volkmar-kantor ,

So to confirm the advice re:
```
Fatal error: Uncaught Error: Division by zero
in ../wp-content/plugins/crop-thumbnails/functions/save.php on line 475
```
Is to downgrade to 1.8.x for now?

All the Best,
Alex
Plugin Author Volkmar Kantor
(@volkmar-kantor)

5 months ago
@alexgwcog yeah please try a downgrade for now, and post the image-sizes you use for cropping.
- This reply was modified 5 months ago by Volkmar Kantor.
Plugin Author Volkmar Kantor
(@volkmar-kantor)

5 months ago

I just tested with an fresh local ddev-wordpress setup and had not the slicest problem.

– PHP 8.2.22
– PHP memory limit 1024M
– nginx/1.26.1
– WP_Image_Editor_Imagick

@mariachellini, @alexgwcog can you please post your server settings?
Thread Starter mariachellini
(@mariachellini)

5 months ago
@volkmar-kantor values taken from the site health info inside WP:

Server: Apache (Linux 6.1.0-26-amd64 x86_64)
PHP: 8.2.24 (Supports 64bit values)
PHP memory limit: 128M, for admin screens: 256M
Is the Imagick library available? No
Active Editor: WP_Image_Editor_GD

I’ll also gladly provide you with any php errors if you can let me know how/where I can get them (I’m not a developer unfortunately ^^)
- This reply was modified 5 months ago by mariachellini.
Plugin Author Volkmar Kantor
(@volkmar-kantor)

5 months ago

@mariachellini ok, thank you, thats interessting – its not the server – as yours is an apache.

In the meantime i found something that may be the reason behind the problem. Thanks to the error message and line @alexgwcog provided.

Hope to get this fixed soon.
alexgwcog
(@alexgwcog)

5 months ago
Hey @volkmar-kantor

Thanks, glad the trace was useful!

In terms of sizes on this site:
```
add_image_size('supporter-logo', 480, 480, false);
add_image_size('person-profile', 480, 563, true);
add_image_size('person-profile-square', 480, 480, true);
add_image_size('mobile', 480, 630, true);
add_image_size('listing-thumbnail', 768, 522, true);
add_image_size('medium-slide', 9999, 600, false);
add_image_size('large-slide', 1200, 675, true);
add_image_size('large-slide-21', 1200, 600, true);
add_image_size('large-slide-flex', 1200, 675, false);
add_image_size('xxl-slide-11', 2000, 2000, false);
add_image_size('xxl-slide-21', 2000, 1000, true);
add_image_size('xxl-slide-31', 2000, 667, true);
add_image_size('large-slide-portrait', 9999, 675, false);
```
And server settings, it’s across 3 balanced nodes that share storage each is:
```
Web server nginx/1.14.1
PHP version	8.1.29 (Supports 64bit values)
PHP SAPI 	fpm-fcgi
PHP max input variables	1000
PHP time limit	90
PHP memory limit	256M
```
And Image Processing:
```
Active editor	EWWWIO_Imagick_Editor
ImageMagick version number	1692
ImageMagick version string	ImageMagick 6.9.12-50 Q16 x86_64 17254 https://legacy.imagemagick.org
Imagick version	3.7.0
```
koendoit
(@koendoit)

5 months ago
Hi @volkmar-kantor,

For me it’s a conflict with another plugin: https://roots.io/products/soil/. If you scroll down to the section: Root relative URLs, that’s the problem. When I disable this, everything works fine.

Thanks for your time.
- This reply was modified 5 months ago by koendoit.
- This reply was modified 5 months ago by koendoit.
Plugin Author Volkmar Kantor
(@volkmar-kantor)

5 months ago

Version 1.9.2 should address the issues of @alexgwcog and @mariachellini. Please try the new version and report if you experience any problems.

Thread Starter mariachellini
(@mariachellini)

5 months ago

@volkmar-kantor with version 1.9.2 the issue is gone, cropping works fine again

thanks a lot for the fix

jhtjards
(@jhtjards)

5 months ago

@volkmar-kantor Did you just miss it or is there another reason for not implementing the rename() atomic-save fix? (Just want to make sure it doesn’t get lost)

alexgwcog
(@alexgwcog)

5 months ago

Hi @volkmar-kantor ,

Amazing, can confirm that that fix works for us and our clients. Thanks so much for the quick response and patch.

All the Best,
Alex

Plugin Author Volkmar Kantor
(@volkmar-kantor)

5 months ago

@jhtjards you right, i totally forgot, sorry about that. So be prepared for version 1.9.3.

Plugin Author Volkmar Kantor
(@volkmar-kantor)

5 months ago

Version 1.9.3 is live. @jhtjards this should fix your problem.

@koendoit please test with Version 1.9.3 – if the error still persists please create a new support ticket.

jhtjards
(@jhtjards)

5 months ago

1.9.3 works great for me, thanks again for your responsiveness!
celsojunior
(@celsojunior)

3 months, 3 weeks ago
Hey there!

I just tested all 1.9.x versions and they all still show the server error. Only version 1.8.0 is OK.
```
nginx version: freenginx/1.27.3
mysql Ver 15.1 Distrib 10.6.20-MariaDB, for debian-linux-gnu (x86_64) using EditLine wrapper
PHP 8.3
```