• signelazer

    (@signelazer)


    Hello, I can’t crop the image, the image remains the same in version 1.9.4 I lowered the version to 1.8 and no problem with this version. I use AWS (as plugins: EWWW Image Optimizer and WP Offload Media Lite).

    Thank you in advance

Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Author Volkmar Kantor

    (@volkmar-kantor)

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

    Thread Starter signelazer

    (@signelazer)

    Hello, no errors in the console, and the request for crop is ok: main.js?ver=1.9.4:73 XHR finished loading: POST “https://******************.net/wp-json/crop_thumbnails/v1/crop”. but the image is the same … no cropped

    • This reply was modified 3 weeks ago by signelazer.
    Thread Starter signelazer

    (@signelazer)

    Hello any news ? you need an staging website? we got the same problem on all website site using aws storage, working good on version 1.8 so i downgraded all our website

    thank you in advance

    Plugin Author Volkmar Kantor

    (@volkmar-kantor)

    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/

    Thread Starter signelazer

    (@signelazer)

    Thank you sended

    Plugin Author Volkmar Kantor

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

    kingja3

    (@kingja3)

    I have the same issue with s3 offload and versions 1.9.0 and above.
    It can be resolved by replacing wp_get_original_image_path to wp_get_original_image_url in the functions involved in save.php and editor.php. Although im not sure if thats a good solution for all cases.

    Thread Starter signelazer

    (@signelazer)

    Nice, maybe @volkmar-kantor can check you’re suggestion and put it in the next update, It would save us having to make a fork and no longer benefit from updates. Thank you in advance

    Plugin Author Volkmar Kantor

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

    Thread Starter signelazer

    (@signelazer)

    @kingja3 i checked you’re solution but change nothing for me, can you send me the zip of you’re plugin modified ? [email protected] i tested with 1.9.5 thank you in advance

Viewing 10 replies - 1 through 10 (of 10 total)
  • You must be logged in to reply to this topic.