• Resolved milenyums

    (@ozguryaazici)


    I’m having trouble with webp at litespeed. I am using google cloud storage with wp-stateless plugin. when i upload a photo it doesn’t create webp immediately. how can i solve this. I also use elementor. It should sync automatically. Could you help? first uploaded photo is loading gcp. but it won’t load because webp is not created.

Viewing 15 replies - 1 through 15 (of 15 total)
  • Thread Starter milenyums

    (@ozguryaazici)

    Plugin Support qtwrk

    (@qtwrk)

    what do you mean by “doesn’t create webp immediately” ? like it will create it later on ?

    Thread Starter milenyums

    (@ozguryaazici)

    no. then it doesn’t. Images are uploaded to google drive. then the webp version is not created.

    Thread Starter milenyums

    (@ozguryaazici)

    CDN
    Copy media files to Google Storage and serve them directly from there.

    Ephemeral
    Store and serve media files with Google Cloud Storage only. Media files are not stored locally, but local storage is used temporarily for processing and is required for certain compatibilities, generating thumbnails for PDF documents.

    I tried both of these options.

    Thread Starter milenyums

    (@ozguryaazici)

    also css files are not generated automatically when there is a change in the elementor page. We added a button on a page. button was not visible. then i went to elementor tools page. I rebuilt. I went to the wp-stateless page. I pressed the run button again for the compatibility files.

    Plugin Support qtwrk

    (@qtwrk)

    if the upload was directly offload to storage , then in this case, image optimization won’t work

    did you enable UCSS or load async css ? if these 2 options were enabled , you may need to explicitly to purge UCSS/CCSS to update the change

    Thread Starter milenyums

    (@ozguryaazici)

    then how will it work with wp-stateless?

    Plugin Support qtwrk

    (@qtwrk)

    actually I just ran a test with it , and it works out of box

    10/10/22 23:50:42.068 [123.123.123.123:65517 1 567] [Media] - replaced to: https://storage.googleapis.com/xxxx/2022/10/6e241175-screenshot2022-10-11-01.34.25-1024x498.png.webp
    10/10/22 23:50:42.068 [123.123.123.123:65517 1 567] [Media] webp replacing: https://storage.googleapis.com/xxxx/2022/10/6e241175-screenshot2022-10-11-01.34.25-300x146.png
    10/10/22 23:50:42.069 [123.123.123.123:65517 1 567] [Util] external
    10/10/22 23:50:42.069 [123.123.123.123:65517 1 567] [Util] external
    10/10/22 23:50:42.069 [123.123.123.123:65517 1 567] [Media] - replaced to: https://storage.googleapis.com/xxxx/2022/10/6e241175-screenshot2022-10-11-01.34.25-300x146.png.webp
    10/10/22 23:50:42.069 [123.123.123.123:65517 1 567] [Media] webp replacing: https://storage.googleapis.com/xxxx/2022/10/6e241175-screenshot2022-10-11-01.34.25-768x374.png
    10/10/22 23:50:42.069 [123.123.123.123:65517 1 567] [Util] external
    10/10/22 23:50:42.069 [123.123.123.123:65517 1 567] [Util] external
    10/10/22 23:50:42.069 [123.123.123.123:65517 1 567] [Media] - replaced to: https://storage.googleapis.com/xxxx/2022/10/6e241175-screenshot2022-10-11-01.34.25-768x374.png.webp
    10/10/22 23:50:42.069 [123.123.123.123:65517 1 567] [Media] webp replacing: https://storage.googleapis.com/xxxx/2022/10/6e241175-screenshot2022-10-11-01.34.25-1536x747.png
    10/10/22 23:50:42.069 [123.123.123.123:65517 1 567] [Util] external
    10/10/22 23:50:42.069 [123.123.123.123:65517 1 567] [Util] external
    10/10/22 23:50:42.069 [123.123.123.123:65517 1 567] [Media] - replaced to: https://storage.googleapis.com/xxxx/2022/10/6e241175-screenshot2022-10-11-01.34.25-1536x747.png.webp
    10/10/22 23:50:42.069 [123.123.123.123:65517 1 567] [Media] webp replacing: https://storage.googleapis.com/xxxx/2022/10/6e241175-screenshot2022-10-11-01.34.25-600x292.png
    10/10/22 23:50:42.069 [123.123.123.123:65517 1 567] [Util] external
    10/10/22 23:50:42.069 [123.123.123.123:65517 1 567] [Util] external
    10/10/22 23:50:42.069 [123.123.123.123:65517 1 567] [Media] - replaced to: https://storage.googleapis.com/xxxx/2022/10/6e241175-screenshot2022-10-11-01.34.25-600x292.png.webp
    10/10/22 23:50:42.069 [123.123.123.123:65517 1 567] [Media] webp replacing: https://storage.googleapis.com/xxxx/2022/10/6e241175-screenshot2022-10-11-01.34.25.png
    10/10/22 23:50:42.069 [123.123.123.123:65517 1 567] [Util] external
    10/10/22 23:50:42.069 [123.123.123.123:65517 1 567] [Util] external
    10/10/22 23:50:42.069 [123.123.123.123:65517 1 567] [Media] - replaced to: https://storage.googleapis.com/xxxx/2022/10/6e241175-screenshot2022-10-11-01.34.25.png.webp

    did you enable LiteSpeed Cache compatibility in WP Stateless setting ?

    Thread Starter milenyums

    (@ozguryaazici)

    yes I have it enabled. How did this happen? what could i have done wrong?

    Thread Starter milenyums

    (@ozguryaazici)

    View post on imgur.com

    I have uploaded 2 images. Can you check one? I uploaded a new file to the site. and webp didn’t render right away. What can I do to create it quickly?

    Plugin Support qtwrk

    (@qtwrk)

    I’d appreciate it if you can translate that screenshot to English …

    but from what it shows , and from the position of text, I guess is that you need to finish all the previous images first before you can optimize the newly uploaded ones.

    Thread Starter milenyums

    (@ozguryaazici)

    View post on imgur.com

    Can you check again? now there is a situation. I blocked the sizes of the photos. There are no different sizes. There is only the original photo. so it needs to do it faster. but webp is created late.

    sometimes it doesn’t happen at all.

    Plugin Support qtwrk

    (@qtwrk)

    no , not the setting page, but the first tab on the image optimization tab

    Thread Starter milenyums

    (@ozguryaazici)

    There are two pictures in the link. Can you check?

    Plugin Support qtwrk

    (@qtwrk)

    it looks like your image optm is not working properly , it always stuck in that status ? the number doesn’t increase ?

    please provide the report number , you can get it in toolbox -> report -> click “send to LiteSpeed”

Viewing 15 replies - 1 through 15 (of 15 total)
  • The topic ‘I’m having trouble with webp at litespeed.’ is closed to new replies.