Hi @nikulv, thanks for reaching out!
I have seen some similar messages in the past related to incomplete installations, although the file affected was different to this case. It might still be worth deactivating and reactivating the plugin, which would force any missing tables/fields to be generated if there had been a problem with WordPress completing the installation originally.
If that doesn’t resolve it, it might help our QA team identify whether anything needs addressing if they have a diagnostic report from your site. You can send that to wftest @ wordfence . com from the top of the Wordfence Tools > Diagnostics page. Click on “Send Report by Email”.
Please add your forum username where indicated and respond here if you do send one as the inbox is unmonitored.
Many thanks,
Peter.
We’ve looked into this a little more @nikulv and it can happen when fetching values that don’t have a default, but it’s normally suppressed by @ in code. You must have a custom error handler that’s causing it to get logged, but we have scheduled a proposed fix for it in a future plugin version.
We’re unable to follow-up on development requests here on the forums so we set topics to “resolved”. It is still an open request in our internal issue tracker, so will document alterations to future plugin versions in our changelog.
Thanks again,
Peter.
