• Resolved KvnKrft

    (@kvnkrft)


    Is there any way I can turn off the debug.log akismet entries? Whenever we enable debug logging, our logs get filled with entries from akismet, apparently triggered by non-problematic comments. It’s nice to have debug details, but there are no issues with akismet and the logs are so cluttered with akismet stuff, it makes it really hard to follow other things in the log.

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

    (@cfinke)

    Yes; to disable Akismet logging when you have WP_DEBUG_LOG turned on, add a filter on akismet_debug_log that returns false:

    
    add_filter( 'akismet_debug_log', '__return_false' );
    

    Just as a note, I am seeing this across many sites right now on hosts all over the world. Debug logs are growing up to 500 MB in very short periods of time and users aren’t aware of it. When they run in to an actual issue, the file is difficult to process due to it’s size. It is my humble opinion that you should reconsider logging so much when there is no actual error occurring.

    Thanks for all your hard work with Akismet!

    Plugin Author Christopher Finke

    (@cfinke)

    @wfasa You’re right. I’ve been thinking about the same issue, and your comment reminded me to do something about it. In the next Akismet update, Akismet debugging will be disabled by default.

    Sounds great Christopher. It will help us work with our WordPress users debugging their sites. Thanks for getting back to me!

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

The topic ‘Clutter in debug.log’ is closed to new replies.