• Resolved Saga Nilsson

    (@sexleksakenadmin8192)


    Many people seem to have a problem with the “Image pull process failure: Failed to pull image [url]” when using image optimization. This never seems to get resolved in the actual plugin. Instead, I’ve seen you are encouraging people to use a temporary fix. This is what you’ve said several times

    edit file?/wp-content/plugins/litespeed-cache/src/img-optm.cls.php?, at line 1162 , you will see?5.6.0?, change it to?8.6.0
    then go to image optm , clean up unfinished data, and send it again

    Changing it makes no difference in my case. If you look at the print below, look in the far bottom left. it seems as though the code is broken somewhere (see “javascript:;“) when I hover over “clean up unfinished data”. I haven’t been able to optimize images for a long time. This problem has persisted for many months now so I’m starting to lose hope that it will ever be resolved. But I hope it will.

    It seems to be a problem related to link management backend, most likely related to how the keys, or specific settings, in the image optimization module are loaded and/or synchronized.

    I would appreciate help.

    Image pull process failure: Failed to pull image [url]
Viewing 1 replies (of 1 total)
  • Plugin Support qtwrk

    (@qtwrk)

    yes , that was a temp solution , we never be able to get our hand on a site that user is willing to debug with us further.

    that javascript:; is normal though , once you clean up and with that 5.6 -> 8.6 change, you should be able to send image again and pull it back , in which this change makes it from Request library fallback to wp_remote_get() function which is proven to be reliable

    the issue is the WordPress’ Request library that doesn’t work on some server , but sadly I can not reproduce it on my server

    if you are willing to help us to debug further on this , please create a ticket by mail to support at litespeedtech.com with reference link to this topic

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