Hi @criscp, thanks for the detailed message.
As this is a PHP Warning, it’s non-fatal and shouldn’t affect the operation of your site. Some customers need to use .user.ini rather than .htaccess to optimize the Wordfence firewall so there are some checks in place to use it where appropriate.
It’s less expensive on resources for us to try opening a file or database record (rather than check for its existence first) and ignore any errors that follow using WordPress’ inbuilt function $wpdb->suppress_errors() or PHP’s @. Some custom error handlers don’t observe these and report the issue anyway, which it looks like you’re seeing here.
Thanks,
Peter.
No problem @criscp! If you have any Wordfence questions in future by all means start up a new topic and we’ll always be happy to help.
Peter.