Missing wordfence/lib/wfVersionSupport.php file

Support
,
1

This is a new installation of Local, and the first site to be installed on it.

Local won’t open the site because it can’t find the file C:\Users\kibbi\Local Sites\saratoga-community-band\app\public\wp-content\plugins\wordfence/lib/wfVersionSupport.php.

I have checked, and the /lib directory doesn’t exist inside the wordfence directory, so of course the wfVersionSupport.php file isn’t there either.

What steps can be taken to replicate the issue? Feel free to include screenshots, videos, etc

Attempting to open the site in Local results in this error. Here is the full error text:

Fatal error: Uncaught Error: Failed opening required ‘C:\Users\kibbi\Local Sites\saratoga-community-band\app\public\wp-content\plugins\wordfence/lib/wfVersionSupport.php’ (include_path=‘.:/usr/share/php:/www/wp-content/pear’) in C:\Users\kibbi\Local Sites\saratoga-community-band\app\public\wp-content\plugins\wordfence\wordfence.php:70 Stack trace: #0 C:\Users\kibbi\Local Sites\saratoga-community-band\app\public\wp-settings.php(560): include_once() #1 C:\Users\kibbi\Local Sites\saratoga-community-band\app\public\wp-config.php(103): require_once(‘C:\\Users\\kibbi\\…’) #2 C:\Users\kibbi\Local Sites\saratoga-community-band\app\public\wp-load.php(50): require_once(‘C:\\Users\\kibbi\\…’) #3 C:\Users\kibbi\Local Sites\saratoga-community-band\app\public\wp-blog-header.php(13): require_once(‘C:\\Users\\kibbi\\…’) #4 C:\Users\kibbi\Local Sites\saratoga-community-band\app\public\index.php(17): require(‘C:\\Users\\kibbi\\…’) #5 {main} thrown in C:\Users\kibbi\Local Sites\saratoga-community-band\app\public\wp-content\plugins\wordfence\wordfence.php on line 70

System Details

  • Local Version: 10.0.0+6907

  • Operating System (OS) and OS version: Windows 10 Home Version 22H2, OS Build 19045.7184

Local Logs

Attach your Local Logs here (Help Doc - Retrieving Local’s Log)

local-logs.zip (17.6 KB)

Security Reminder
Local does a pretty good job of scrubbing private info from the logs and the errors it produces, however there’s always the possibility that something private can come through. Because these are public forums, always review the screenshots you are sharing to make sure there isn’t private info like passwords being displayed.

2

Hi @fmk2 - If you click on Site Shell (under your site name in the Local app) you can run a command like this to disable Wordfence:

wp plugin deactivate wordfence

Another way to do this is by navigating to the Wordfence plugin folder directly and renaming it to something like wordfence-old which will effectively disable it as well.

3

Using that command resulted in a different error, but renaming the Wordfence folder seems to have worked.

Thanks for the help.

Frank

4

Glad to hear it @fmk2! Thank you for the update