Volkmar Kantor

@kingja3 thank you for investigating. Yeah i remembered that this function was changed, cause in an strict php environment this will throw an error (try to read an image from an url instead from the file-system may be a security risk). Will have a look on it. I guess we need an admin-option for this.

@signelazer in the meantime, you may change replace the usage from wp_get_original_image_path?to wp_get_original_image_url?in your /wp-content/plugins/crop-thumbnails/functions/save.php. Let me know if its working.

• This reply was modified 4 days, 6 hours ago by Volkmar Kantor.
• This reply was modified 4 days, 6 hours ago by Volkmar Kantor.

I had a look on your server and tested version 1.8.0 and version 1.9.5.

You worked on an server with CDN-Synchronisation and a quit complex setup.

As you stated version 1.9.5 do not to show a different image after cropping.

When cropped with 1.8.0 the old image is no longer visible (CDN do not have the image anymore). So there is a different behavior, but i can not confirm that it was working with 1.8.0. I left this version on your system.

In the end, my plugin do not support a CDN based file-system out of the box. If you experience problem with this plugin you may be on your own. As i do not use CDN based systems for my own i could not help you. You may have a look on the github page of the plugin (https://github.com/vollyimnetz/crop-thumbnails) i added a lot of filters and hooks to the save procedure. You may trigger CDN file synchronization on you own, after the plugin cropped the image.

Sorry, totally forget about this ticket.

I wonder why the plugin worked in the first place. It would normally not work with a cloud storage, except the plugin has some code to update the image after the crop is finished. If you could grant me some access to a staging website i could have a look on it. You may get in contact with me on this address: https://www.totalmedial.de/kontakt/

Open the browser developer console, is there any “cross origin request” error/warning?

Fixed in Version 1.9.4

Hi @tahninial,

thank you for reporting and the detailed explanation how to reproduce.

I can confirm the problem, will have a look into that in the next days.

Please test if version 1.8.0 is working. You may download this version from the github releases: https://github.com/vollyimnetz/crop-thumbnails/releases

If version 1.8.0 is not working, than you have another problem.

I would assume there is some cross-origin-access problem. You may check in the developer console of your browser if there is an cross-origin-access message in the Javascript-Console-Log.

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 you right, i totally forgot, sorry about that. So be prepared for version 1.9.3.

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

Version 1.9.2 will make the plugin compatible with older versions of wordpress again.

@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.

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?

@alexgwcog yeah please try a downgrade for now, and post the image-sizes you use for cropping.

• This reply was modified 1 month ago by Volkmar Kantor.

@koendoit ok, i will investigate with a ddev setup on my own.

Seems that there are maybe multiple problems. You may use version 1.8.0 in production till this is fixed.

@alexgwcog could you please post your image settings (what resolutions do you crop for)?

• This reply was modified 1 month ago by Volkmar Kantor.
• This reply was modified 1 month ago by Volkmar Kantor.