• Hello,

    I have v1.7.7. The error logs displaying on the dashboard can not be cleared. Here is the error logs:

    Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /home/SorryHided/SorryHided.com/wp-includes/functions.php on line 7127

    Deprecated: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /home/SorryHided/SorryHided.com/wp-includes/functions.php on line 2182

    Please help. Thanks in advance!

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Janis Elsts

    (@whiteshadow)

    Can you elaborate on what exactly happens when you try to clear the log? If there is an error of some kind, please post it.

    Also, please check the error timestamps (if available) to see if these errors that are just getting logged repeatedly all the time. In that case, clearing the log wouldn’t help much since it would get filled with the same errors again.

    Thread Starter cfm168

    (@cfm168)

    Thank you for quick response. Yes the same error logs repeatedly show up. The problem is I can’t completely clear them up from dashboard even once, this is what I want to report here.

    Aug 17, 10:12:31
    
    Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /home/SorryHided/SorryHided.com/wp-includes/functions.php on line 7127
    
    Aug 17, 10:12:31
    
    Deprecated: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /home/SorryHided/SorryHided.com/wp-includes/functions.php on line 2182
    
    Aug 17, 10:12:31
    
    Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /home/SorryHided/SorryHided.com/wp-includes/functions.php on line 7127
    
    Aug 17, 10:12:31
    
    Deprecated: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /home/SorryHided/SorryHided.com/wp-includes/functions.php on line 2182
    
    Aug 17, 10:13:41
    
    Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /home/SorryHided/SorryHided.com/wp-includes/functions.php on line 7127
    
    Aug 17, 10:13:41
    
    Deprecated: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /home/SorryHided/SorryHided.com/wp-includes/functions.php on line 2182
    
    Aug 17, 10:13:41
    
    Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /home/SorryHided/SorryHided.com/wp-includes/functions.php on line 7127
    
    Aug 17, 10:13:41
    
    Deprecated: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /home/SorryHided/SorryHided.com/wp-includes/functions.php on line 2182
    
    Aug 17, 10:17:25
    
    Deprecated: Hook login_headertitle is deprecated since version 5.2.0! Use login_headertext instead. Usage of the title attribute on the login logo is not recommended for accessibility reasons. Use the link text instead. in /home/SorryHided/SorryHided.com/wp-includes/functions.php on line 5828
    
    Aug 17, 10:17:56
    
    Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /home/SorryHided/SorryHided.com/wp-includes/functions.php on line 7127
    
    Aug 17, 10:17:56
    
    Deprecated: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /home/SorryHided/SorryHided.com/wp-includes/functions.php on line 2182
    Plugin Author Janis Elsts

    (@whiteshadow)

    Unfortunately, if the same errors keep getting logged again and again, clearing the log file won’t be effective. Even when you do it successfully, the log will just get filled with new copies of the same errors soon.

    The ideal way to fix it would be to fix whatever is causing those errors. However, since all of them seem to happen in WordPress core files, it might be hard to figure out what the true cause is. In theory, you could deactivate all plugins, see if new errors stop showing up, then reactivate plugins one by one to see which one causes errors be logged again. This may not be practical on a live site.

    If it’s not possible to find and fix the source of the errors, you could use the “ignore” option to hide them instead. The messages will stay in the file, and new copies can still be logged, but they should not show up in the dashboard widget.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Can not clear logs’ is closed to new replies.