Wordfence 5.3.1 Released with full documentation, updated Geo DB and Improved Export
Wordfence 5.3.1 has just been released. We’re excited to announce that Wordfence is now fully documented. That may not sound like a big deal, but it is a Big Deal.
docs.wordfence.com which is our new Official Documentation website for Wordfence now has approximately 25,000 words of documentation that cover all aspects of Wordfence and our API. Most of this was added during the past 2 weeks.
More importantly, links to all relevant documentation pages and sub-sections have been added in all the right places in the newest Wordfence release. This has also allowed us to remove lots of extraneous text that was getting in the way because you can now get all the info you need on the docs website.
This version of Wordfence also has our November 5th, 2014 IP 2 Country database which is the very latest and will ensure that our customers using country blocking are getting the most reliable performance available for blocking countries.
We’ve also improved our new Wordfence Options Import/Export feature which now also includes your scan scheduling and country blocking configuration when doing an export and import.
Thanks for being part of Wordfence!!
Comments
7:17 pm
Your email came about 12 hours too late. WordFence thought I had 5.2.9 installed when it checked my 5.3.1 files against the 5.2.9 source code. I managed to figure out what was going on before i restored all the files back to 5.2.9.
7:31 pm
Hi Steven. Wordfence is version aware when it does core, theme or plugin comparisons, so not sure what issue you had, but please post in our support forums and we'll investigate.
7:02 am
I am not worried about it. I think the WordFence update happened at about the same time the scan was going on. I compared the time that the change was first noticed to the time of the last update. They were very close. I am sure the problem has fixed itself. Luckily in my investigation of the situation before I made any changes, I noticed that the version that WordFence checked against was not the version that WordFence said was currently installed. I did further checking because there were a lot of files involved and the changes in the first file did not look malicious.
You might want to put some thought in what WordFence ought to do when this coincidence happens.