PHP Log, [DEBUG] : Should we use webp?

  • Resolved backpackingseries

    (@backpackingseries)


    4 years ago

    Hi Support,

    Thank you for helping to release version 3.2.5 – sites are stable now. However, I am witnessing a new PHP record – PHP Log, [DEBUG] : Should we use webp?

    This is being written to the log continuously. If I disable your plugin, the problem goes away.

    How can I avoid this please?

    Kind regards,

Viewing 8 replies - 1 through 8 (of 8 total)
  • webmasterfreya

    (@webmasterfreya)

    4 years ago

    Very very bad idea to notify the users of this plugin this way to tell that there is a new function. Every request creates an entry in the php error log.

    I’ve put under settings “Log events to the PHP error log ” off

    Harshad

    (@bornforphp)

    4 years ago

    @webmasterfreya @backpackingseries I’ll check this issue with our development team and update you soon.

    Thank you for your time and patience.

    Jim

    (@jwmc)

    4 years ago

    My log looks like this: constant stream

    [06-Jun-2022 14:30:02 UTC] [DEBUG] : Setting up .htaccess file
[06-Jun-2022 14:30:02 UTC] [DEBUG] : Should we use webp? 
[06-Jun-2022 14:30:02 UTC] [DEBUG] : 
[06-Jun-2022 14:30:09 UTC] [DEBUG] : Setting up .htaccess file
[06-Jun-2022 14:30:12 UTC] [DEBUG] : Setting up .htaccess file
[06-Jun-2022 14:30:12 UTC] [DEBUG] : Should we use webp? 
[06-Jun-2022 14:30:12 UTC] [DEBUG] : 
[06-Jun-2022 14:30:13 UTC] [DEBUG] : Setting up .htaccess file
[06-Jun-2022 14:30:13 UTC] [DEBUG] : Should we use webp? 
[06-Jun-2022 14:30:13 UTC] [DEBUG] : 
[06-Jun-2022 14:30:54 UTC] [DEBUG] : Setting up .htaccess file
[06-Jun-2022 14:30:55 UTC] [DEBUG] : Should we use webp? 
[06-Jun-2022 14:30:55 UTC] [DEBUG] :
    Plugin Contributor Venkat Raj

    (@webulous)

    4 years ago

    Hi @backpackingseries @webmasterfreya @jwmc

    Since not every browser supports webp images and nginx servers don’t support .htaccess redirect, it is necessary to check things with every request.

    Apart from that these are [DEBUG] messages and debug logging shouldn’t be enabled in production sites unless site is not working properly and you want to provide debugging info to developers.

    That said, we will remove these entries in the upcoming version

    spiros

    (@spiros)

    4 years ago

    Same with me, thousands of these entries. Debug is off in

    Jim

    (@jwmc)

    4 years ago

    @webulous, thanks for the response. Regular debug monitoring is debatable, but I won’t do that here. I do want to make the point that I have all the image processing features of WP Optimize turned off. I use it only for cache and minify. If the plugin were efficient, then, I would expect it would not be chasing the image processing issues every few seconds and that part of the code would not be called at all, whether it shows up in the debug log or not.

    Thread Starter backpackingseries

    (@backpackingseries)

    4 years ago

    Thank you @webulous

    I’m not using the plugin’s image processing module at this time. Therefore, I’m hoping it should not log such messages.

    Kind regards,

    Harshad

    (@bornforphp)

    3 years, 12 months ago

    @backpackingseries This should be fixed in next release

Viewing 8 replies - 1 through 8 (of 8 total)

The topic ‘PHP Log, [DEBUG] : Should we use webp?’ is closed to new replies.