EWWW_IMAGE_OPTIMIZER_AUX_PATHS and XAMPP

  • Resolved enkirch

    (@enkirch)


    1 year, 4 months ago

    Hi,
    I would like to use “EWWW_IMAGE_OPTIMIZER_AUX_PATHS”.
    But for that I would have to test it locally first. Local means xampp for me.

    On settings page I have under “Folders to Optimize” the partial path as follows.

    “D:\xampp-7-3-14\htdocs\abcd/”

    The thing that is missing now is the part “wp-content\user-uploads-2022\2023\07”.

    But these two attempts

    D:\xampp-7-3-14\htdocs\abcd\wp-content\user-uploads-2022\2023\07
    D:\xampp-7-3-14\htdocs\abcd/wp-content/user-uploads-2022/2023/07
    D:\xampp-7-3-14\htdocs\abcd/wp-content/user-uploads-2022/2023/07/

    do not work.

    The first path ends in the input field saying only “D:\xampp-7-3-14\htdocs\abcd/”.

    With the 2nd and 3rd path there is nothing in the input field, only the notice “Undefined variable: file” in the file wp-content/plugins/ewww-image-optimizer/common.php:4084 and wp-content/plugins/ewww-image-optimizer/common.php:4085

Viewing 1 replies (of 1 total)
  • Plugin Author nosilver4u

    (@nosilver4u)

    What version of the plugin are you using? Lines 4084 and 4085 do not have any such code in 7.1 or 7.2.

    Do note that whatever you define for EWWW_IMAGE_OPTIMIZER_AUX_PATHS should override what is shown on the settings, if you have specified it properly as an array.

    You can also use relative paths when you define it, so wp-content\user-uploads-2022\2023\07 should be just fine, and should then display as a full path on the settings page. To my knowledge, PHP is not generally picky about the direction of the slashes on Windows and should be able to figure things out just fine.

    I would use all forward slashes though, as a backslash might be interpreted as an escape character and yield unexpected results.

Viewing 1 replies (of 1 total)
  • The topic ‘EWWW_IMAGE_OPTIMIZER_AUX_PATHS and XAMPP’ is closed to new replies.