Hi FrogStoneMedia,
Is this a WordPress installation in a sub-directory of another WordPress installation? if so, make sure to update Wordfence on the other site as well.
Also, you might need to check the paths of files loaded in “wordfence-waf.php” file to make sure they are pointing to the correct ones, along with the path to “wordfence-waf.php” file itself in “auto_prepend_file” option in .htaccess/.user.ini file depending on your server configuration.
Thanks.
Hey,
This is a /public_html/ install and no MU. Below are pasted contents. They are all defaults and unmodified from the previous version. Recommendations from here?
// .user.ini:
; Wordfence WAF
auto_prepend_file = ‘/home/USERNAME/public_html/wordfence-waf.php’
; END Wordfence WAF
// .htaccess:
# Wordfence WAF
<Files “.user.ini”>
<IfModule mod_authz_core.c>
Require all denied
</IfModule>
<IfModule !mod_authz_core.c>
Order deny,allow
Deny from all
</IfModule>
</Files>
# END Wordfence WAF
//wordfence-waf.php:
<?php
// Before removing this file, please verify the PHP ini setting auto_prepend_file does not point to this.
if (file_exists(‘/home/USERNAME/public_html/wp-content/plugins/wordfence/waf/bootstrap.php’)) {
define(“WFWAF_LOG_PATH”, ‘/home/USERNAME/public_html/wp-content/wflogs/’);
include_once ‘/home/USERNAME/public_html/wp-content/plugins/wordfence/waf/bootstrap.php’;
}
?>
Just wanted to make sure that you tried to completely uninstall Wordfence, then re-installing it again and you encounter the same error?
It could be a problem in PHP OPcache that keeps caching a pre-compiled version of the old files instead of the new ones, restarting PHP should clear the OPcache and fix this issue, you can get in contact with your hosting provider to do that in case you aren’t managing this server on your own.
Thanks.
Good call on OPcache! I’m using WP Rocket / Memcached Redux and used WP Rocket to clear the cache. Install + Activation worked after that. No restart required 🙂
>>Just wanted to make sure that you tried to completely uninstall Wordfence, then re-installing it again and you encounter the same error?
Yes to producing the same error.
