Forum Replies Created

Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter mariachellini

    (@mariachellini)

    Hello @petredobrescu ,

    just wanted to check if you saw my response and if there’s any news?

    thanks and all the best

    Thread Starter mariachellini

    (@mariachellini)

    Hello Pedro,

    thanks for the quick response.

    To answer your question: I want to be able to manually crop all images (main image + all thumbnail variations) to ensure that all images used are looking good on the site.

    That’s what the Crop Thumbnails Plugin essentially does (https://ww.wp.xz.cn/plugins/crop-thumbnails/). It shows all available image variations and then you can click on it and select a different crop manually that would fit the image. you can also choose to group images with the same ratio together, example: if there are 3 thumbnails with the ratio 2:1. like: 100×50, 400×200 and 800×400 you can either manually crop them individually or have them as a group. then you only need to crop 1 image and the selected area will be applied to all the thumbnails with the same ratio.

    in general your plugin and the crop thumbnail work together (no conflict or error messages), meaning I can still manually crop all images after they were optimized by shortpixel. the issues are in the details:

    – using “smart crop” the preview of the thumbnails shown in crop thumbnails is often wrong (which is problematic since you would choose which one to fix based on the preview)

    – when manually cropping then only the “original” jpg/png versions are changed, the webp/avif version created by shortpixel remain untouched. I’d assume that’s because the other pluign doesn’t know about these variations…

    best solution would be of course if you’d implement manual cropping into shortpixel. then there wouldn’t be a conflict or even the need to use multiple plugins to get images right.

    thanks

    Thread Starter mariachellini

    (@mariachellini)

    sorry to hear, for me both plugins would be great together and not one being a replacement for the other. because while shortpixel does its best trying to auto-crop your crop thumbnail plugin gives the user the manual control to overrule and fix all the images to a users liking.

    for the files: the generated webP files are named exactly as their “original” jpg one’s and are in the same location.

    you wrote you use less cropped image-sizes all together, do you mind sharing what you’re doing instead? Especially when I’m seeing so many themes out there adding 20 image sizes for different modules/layouts etc. it would be great to see a different workflow from a professional like you, because when I could reduce the number of images I’d be all for it 😀

    thanks again

    Thread Starter mariachellini

    (@mariachellini)

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

    thanks a lot for the fix

    Thread Starter mariachellini

    (@mariachellini)

    @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 ^^)

    Thread Starter mariachellini

    (@mariachellini)

    @volkmar-kantor the error happens on all images, even the small 150×150 version. also the error message popup shows up instantly once the “save crop” button is pressed.

    here’s the console error:

    main.js?ver=1.9.0:73

    POST https://local.dev/wp-json/crop_thumbnails/v1/crop 500 (Internal Server Error)

    (anonymous) @ main.js?ver=1.9.0:73

    xhr @ main.js?ver=1.9.0:73

    Nh @ main.js?ver=1.9.0:75

    _request @ main.js?ver=1.9.0:76

    request @ main.js?ver=1.9.0:75

    (anonymous) @ main.js?ver=1.9.0:71

    RT @ main.js?ver=1.9.0:76

    cropThumbnails @ main.js?ver=1.9.0:76

    e.cropData.e.cropData.hiddenOnPostType.e.errorMessage.U.onClick.t.<computed>.t.<computed> @ main.js?ver=1.9.0:76

    Ys @ main.js?ver=1.9.0:25

    In @ main.js?ver=1.9.0:25

    n @ main.js?ver=1.9.0:30

    main.js?ver=1.9.0:76 crop-thumbnails connection error {status: 500, statusText: '', requestUrl: 'https://local.dev/wp-json/crop_thumbnails/v1/crop', requestParams: '{"crop_thumbnails":{"selection":{"x":165,"y":0,"x2…width":150,"height":150,"ratio":1,"crop":true}]}}'}requestParams: "{\"crop_thumbnails\":{\"selection\":{\"x\":165,\"y\":0,\"x2\":742,\"y2\":577,\"w\":577,\"h\":577,\"cropBaseSize\":\"large\"},\"sourceImageId\":115208,\"activeImageSizes\":[{\"name\":\"thumbnail\",\"width\":150,\"height\":150,\"ratio\":1,\"crop\":true}]}}"requestUrl: "https://local.dev/wp-json/crop_thumbnails/v1/crop"status: 500statusText: ""[[Prototype]]: Objectconstructor: ƒ Object()hasOwnProperty: ƒ hasOwnProperty()isPrototypeOf: ƒ isPrototypeOf()propertyIsEnumerable: ƒ propertyIsEnumerable()toLocaleString: ƒ toLocaleString()toString: ƒ toString()valueOf: ƒ valueOf()__defineGetter__: ƒ __defineGetter__()__defineSetter__: ƒ __defineSetter__()__lookupGetter__: ƒ __lookupGetter__()__lookupSetter__: ƒ __lookupSetter__()__proto__: (...)get __proto__: ƒ __proto__()set __proto__: ƒ __proto__()

    (anonymous) @ main.js?ver=1.9.0:76

    Promise.catch

    cropThumbnails @ main.js?ver=1.9.0:76

    e.cropData.e.cropData.hiddenOnPostType.e.errorMessage.U.onClick.t.<computed>.t.<computed> @ main.js?ver=1.9.0:76

    Ys @ main.js?ver=1.9.0:25

    In @ main.js?ver=1.9.0:25

    n @ main.js?ver=1.9.0:30
    Thread Starter mariachellini

    (@mariachellini)

    @richardlampitt Thanks for the suggestion. Just had a look, my WordPress version is 6.6.2. I also tried the plugin’s self-check, but here also all tests were successful.

    For now, I downgraded to plugin version 1.8.0, which is working fine.

Viewing 7 replies - 1 through 7 (of 7 total)