PHP Fatal error: Call to undefined function wp_normalize_path()

Working on this now with the dev team.

tim

@wfsupport, same here with WordPress v.3.8.1

Can confirm the same issue on 3.5.1. No pressure from here since WF has served us so well over the past and WF newsletters have tipped us off on how to stay secure in a scenario like this!

Fatal error: Call to undefined function wp_normalize_path() in /home/outofthe/public_html/wp-content/plugins/wordfence/lib/wfUtils.php on line 106 on line 106

Cheers,
Jack.

Got it. If you are affected by this revert your WF version to 5.3.6, available here:
https://www.ads-software.com/plugins/wordfence/developers/

tim

i cannot enter in the plugin menu, so i deleted the wordfence dir but the problem is still there….what can i do?

Hi, already solved, i cleaned the browser cache… sorry. bye!
Angelo

@all

We just released a new version to address this. Please update and let me know if this fixes your issue.

tim

Thanks! Solved ??

@tim, I am sorry to bother you again but here https://www.ads-software.com/plugins/wordfence/ says “Requires: 3.9 or higher“, so in my WordPress installation which is v.3.8.1, I can’t update through WordPress Dashboard!

So if as it says here https://www.ads-software.com/plugins/wordfence/changelog/

5.3.8
Customers running WP versions older than 3.9 don’t support wp_normalize_path(). Added support for older WP versions to fix an error being thrown.

support has been added for WP versions older than 3.9 why is it required?

Thank you for your time.

P.S
I know that running on a WordPress installation that is not up to date is not a good practice, but that is another story to tell ??

Yep! Solved in 5.3.8.

Thank you very much guys!
Angelo

@kanenas. That is correct. We changed the compatabliltiy requirements to say that, however we patched the plugin to work with the older version of WordPress because we know that it affected some of our users. Going forward we are requiring 3.9 and above. You still should be able to use this version even though it now says that as others seem to have no trouble. If you do, then add the plugin via FTP to update it.

thanks all

Tim

Wow, kick in the teeth for auto-updates!

I’ve just had an irate client on the phone who has only just realised that his site has been offline for two weeks because of this. Please can you put a check for the WordPress version in your plugin so that the auto-update routine stops when the minimum compatibility level of Wordfence goes beyond the version of WordPress that it’s updating itself of – and perhaps fire off an email to the notifications address to state this.

I’m now having to go through 30 other client’s websites to check that they haven’t gone down too.