Debug log turned on

  • Resolved guzart

    (@guzart)


    5 years ago

    It appears that the latest version of EWWW keeps writing a to wp-content/ewww/debug.log. This wasn’t happening before, so I wonder if it was an ommission on the latest release. I did jump from v5.1.4 to 5.2.1.

    2020-02-11 19:21:10
<b>ewww_image_optimizer_settings_script()</b>
<b>ewww_image_optimizer_bulk_script()</b>
<b>ewww_image_optimizer_tool_script()</b>
<b>ewww_image_optimizer_webp_script()</b>
2020-02-11 19:21:47
<b>ewww_image_optimizer_settings_script()</b>
<b>ewww_image_optimizer_bulk_script()</b>
<b>ewww_image_optimizer_tool_script()</b>
<b>ewww_image_optimizer_webp_script()</b>
2020-02-11 19:22:11
<b>ewww_image_optimizer_settings_script()</b>
<b>ewww_image_optimizer_bulk_script()</b>
<b>ewww_image_optimizer_tool_script()</b>
<b>ewww_image_optimizer_webp_script()</b>

    Thank you!

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author nosilver4u

    (@nosilver4u)

    The log has always been used if the debugging option is enabled. You can disable it on the Support tab.

    Do note that there was a point where the log wasn’t being created properly, and we did change the location, but those changes were back in version 4.8.1.

    Thread Starter guzart

    (@guzart)

    Thank you for the quick reply.

    Something must have changed tho. I have the WordPress site in git and the file didn’t exist before and I did not make changes to the settings.

    I do have an EWWW debug.log in my .gitignore, and the location was
    /wp-content/plugins/ewww-image-optimizer/debug.log and the new location is at /wp-content/ewww/debug.log.

    Plugin Author nosilver4u

    (@nosilver4u)

    Hmm, it’s possible there was another bug that prevented the creation of the log, can you test this:
    With debugging option disabled, remove the debug.log file, and see if it gets recreated when you visit the EWWW IO settings page, the bulk optimizer, or any other random page (admin or front-end) on your site.
    It shouldn’t be recreated with debugging disabled, but just want to double-check there isn’t some bug there.

    Thread Starter guzart

    (@guzart)

    No bug there. When the debug setting is disabled it does not create a debug.log file.

    I don’t think I have an issue. It’s only that I found the new location of the debug.log file odd, so I assumed it could’ve been a mistake in the release, not a design choice. AFAIK it’s unusual for plugins to store files directly under the wp-content/ folder, but not unheard of.

    Anyway, thank you for your help!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Debug log turned on’ is closed to new replies.