• Plugin redirect to file /wp-content/webp-express/webp-images/doc-root/wp-content/uploads/2016/07/main43-800×367.jpg.webp

    This file return error “Error occured while calculating destination path: Image root not found”

    File /wp-content/uploads/2016/07/main43-800×367.jpg exist and /wp-content/uploads/2016/07/main43.jpg too

    How I fix it?

    Live test results:
    Testing “WebP Realizer” functionality
    UPLOADS
    Copying JPEG to uploads folder (webp-express-test-images/wCWUbQ.JPEG). ok
    We now have a jpeg stored here:
    /home/dev2/domains/………/public_html/wp-content/uploads/webp-express-test-images/wCWUbQ.JPEG
    Lets check that browsers supporting webp gets a freshly converted WEBP when a non-existing WEBP is requested, which has a corresponding source
    Making a HTTP request for the test image (pretending to be a client that supports webp, by setting the “Accept” header to “image/webp”)
    Request URL: ……./wp-content/webp-express/webp-images/doc-root/wp-content/uploads/webp-express-test-images/wCWUbQ.JPEG.webp
    Response: 200 OK
    Response headers:
    – server: nginx
    – date: Mon, 28 Dec 2020 14:49:54 GMT
    – content-type: text/html; charset=UTF-8
    – content-length: 83
    – x-webp-express-error: Error occured while calculating destination path: Image root not found
    – vary: Accept-Encoding,User-Agent
    – content-encoding: gzip
    – x-hosted-by: https://agho.st
    – strict-transport-security: max-age=63072000; includeSubdomains;
    – x-content-type-options: nosniff

    Body:
    Error occured while calculating destination path: Image root not found
    However. As the “content-type” header reveals, we did not get a webpSurprisingly we got: “text/html; charset=UTF-8”
    The test FAILED.
    Deleting test images
    THEMES
    Copying JPEG to themes folder (webp-express-test-images/yLMQW8.JPEG). ok
    We now have a jpeg stored here:
    /home/dev2/domains/………/public_html/wp-content/themes/webp-express-test-images/yLMQW8.JPEG
    Lets check that browsers supporting webp gets a freshly converted WEBP when a non-existing WEBP is requested, which has a corresponding source
    Making a HTTP request for the test image (pretending to be a client that supports webp, by setting the “Accept” header to “image/webp”)
    Request URL: https://………/wp-content/webp-express/webp-images/doc-root/wp-content/themes/webp-express-test-images/yLMQW8.JPEG.webp
    Response: 200 OK
    Response headers:
    – server: nginx
    – date: Mon, 28 Dec 2020 14:49:54 GMT
    – content-type: text/html; charset=UTF-8
    – content-length: 83
    – x-webp-express-error: Error occured while calculating destination path: Image root not found
    – vary: Accept-Encoding,User-Agent
    – content-encoding: gzip
    – x-hosted-by: https://agho.st
    – strict-transport-security: max-age=63072000; includeSubdomains;
    – x-content-type-options: nosniff

    Body:
    Error occured while calculating destination path: Image root not found
    However. As the “content-type” header reveals, we did not get a webpSurprisingly we got: “text/html; charset=UTF-8”
    The test FAILED.

Viewing 1 replies (of 1 total)
Viewing 1 replies (of 1 total)
  • The topic ‘Don’t create some webp files upon request’ is closed to new replies.