• Resolved Wudman

    (@wudman)


    Well, well, update hell..
    So far I have had to go in and disable WordFence via FTP on three client websites due to this error. This isn’t really an acceptable situation. WordFence is fast to alert us to security fails, but apparently this issue isn’t worth a courtesy email blast.

    The quick fix is to log into your host and rename the WordFence folder. It behooves you to have an FTP login and then this workaround is even faster.

    In the meantime WordFence, fix this…

Viewing 2 replies - 1 through 2 (of 2 total)
  • I checked my site and found the same problem with wordfence. What a mess. I was able to deactivate the plugin and it seems things are okay for the moment, although I’m not confident about letting my site run for very long without it.

    Hi,
    Thanks for bringing this issue to us, it has been already logged to our team and the proper fix will be included in the next update (internal reference number: #FB6659).
    For now if you can see these warnings on the front-end of your website, you can edit “wp-config.php” file and add these lines:

    
    define('WP_DEBUG_LOG', true);
    define('WP_DEBUG_DISPLAY', false);
    

    after this one:
    define('WP_DEBUG', true);

    This will only log the warnings/errors to a file called “debug.log” located in (wp-content) directory and hide them from the front-end.

    Thanks.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Warning: inet_pton(): Unrecognized address…’ is closed to new replies.