• Resolved bviktor

    (@bviktor)


    At first I thought it’s some server configuration issue, then I realized the webp files aren’t even there:

    -rw-r--r--.  1 nginx nginx  31171 Sep  3  2018 migrating-from-dirsync-to-azure-ad-connect-Clipboard09.png
    -rw-r--r--. 1 nginx nginx 25144 Dec 6 22:20 migrating-from-dirsync-to-azure-ad-connect-Clipboard09.png.webp
    -rw-r--r--. 1 nginx nginx 34638 Sep 3 2018 migrating-from-dirsync-to-azure-ad-connect-Clipboard12.png
    -rw-r--r--. 1 nginx nginx 32246 Dec 6 22:20 migrating-from-dirsync-to-azure-ad-connect-Clipboard12.png.webp
    -rw-r--r--. 1 nginx nginx 22043 Sep 3 2018 migrating-from-dirsync-to-azure-ad-connect-Clipboard13.png
    -rw-r--r--. 1 nginx nginx 7974 Sep 3 2018 migrating-from-dirsync-to-azure-ad-connect-Clipboard14.png
    -rw-r--r--. 1 nginx nginx 12400 Sep 3 2018 migrating-from-dirsync-to-azure-ad-connect-Clipboard15.png
    -rw-r--r--. 1 nginx nginx 53158 Sep 3 2018 migrating-from-dirsync-to-azure-ad-connect-Clipboard16.png
    -rw-r--r--. 1 nginx nginx 136534 Sep 3 2018 migrating-from-dirsync-to-azure-ad-connect-Clipboard17.png
    -rw-r--r--. 1 nginx nginx 115350 Sep 3 2018 migrating-from-dirsync-to-azure-ad-connect-Clipboard18.png
    -rw-r--r--. 1 nginx nginx 106590 Dec 6 22:20 migrating-from-dirsync-to-azure-ad-connect-Clipboard18.png.webp
    -rw-r--r--. 1 nginx nginx 117986 Sep 3 2018 migrating-from-dirsync-to-azure-ad-connect-Clipboard19.png
    -rw-r--r--. 1 nginx nginx 116068 Dec 6 22:20 migrating-from-dirsync-to-azure-ad-connect-Clipboard19.png.webp
    -rw-r--r--. 1 nginx nginx 7845 Sep 3 2018 migrating-from-dirsync-to-azure-ad-connect-Clipboard20.png
    -rw-r--r--. 1 nginx nginx 47393 Sep 3 2018 migrating-from-dirsync-to-azure-ad-connect-Clipboard22.png
    -rw-r--r--. 1 nginx nginx 22394 Sep 3 2018 migrating-from-dirsync-to-azure-ad-connect-Clipboard23.png
    -rw-r--r--. 1 nginx nginx 116518 Sep 3 2018 migrating-from-dirsync-to-azure-ad-connect-Clipboard24.png
    -rw-r--r--. 1 nginx nginx 109784 Dec 6 22:20 migrating-from-dirsync-to-azure-ad-connect-Clipboard24.png.webp

    Second guess was that the plugin intelligently skips files below a certain filesize limit, but nope, migrating-from-dirsync-to-azure-ad-connect-Clipboard09.png has a size of 31171 and gets converted, while migrating-from-dirsync-to-azure-ad-connect-Clipboard16.png is 53158 bytes and does not.

    What am I doing wrong? “Convert existing images” won’t find anything new after consecutive runs.

Viewing 1 replies (of 1 total)
  • Thread Starter bviktor

    (@bviktor)

    Ah never mind, added some debug code to images-to-webp.php/convert_image(), it’s because the resulting webp files are bigger than the originals.

    Might be useful to add a “verbose” option to print these during the conversion process:)

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.