Wordfence - WordPress Security Plugins v8.0.5

AliSoleimani_94 said:

wordfence v7.7.0

Click to expand...

purity said:

Tomz updated Wordfence - WordPress Security Plugin with a new update entry:

Wordfence v7.7.1 Nulled



Read the rest of this update entry...

Click to expand...

purity said:

Tomz updated Wordfence - WordPress Security Plugin with a new update entry:

Wordfence v7.7.1 Nulled



Read the rest of this update entry...

Click to expand...

purity said:

Tomz updated Wordfence - WordPress Security Plugin with a new update entry:

Wordfence v7.7.1 Nulled



Read the rest of this update entry...

Click to expand...

Scratchmasta said:

It's great! But it's a very heavy plugin. My website is quite significantly slower after installing.

Click to expand...

Proxybunker said:

if Wordfence is making your site slower then you need better hosting

Click to expand...

Scratchmasta said:

It's great! But it's a very heavy plugin. My website is quite significantly slower after installing.

Click to expand...

Scratchmasta said:

It's great! But it's a very heavy plugin. My website is quite significantly slower after installing.

Click to expand...

What should I do?​

• In the “Basic Options” section, uncheck Enable Live Traffic View if you don’t regularly use that feature
• In the “Scans to include” section, uncheck Scan images, binary, and other files as if they were executable"

​

Snapper123 said:

You could try this...

"The main way Wordfence slows down sites is by repeatedly scanning gigabytes of files like images, .zip backups, and so on. It doesn’t scan these by default, at least in recent versions, because even the authors of Wordfence don’t think it’s necessary, and we agree.
In addition, the Wordfence “Live Traffic View” consumes significant resources and should be disabled if you don’t routinely use it. The Wordfence documentation says that “you may consider disabling live traffic to reduce the load on your web server”.

What should I do?​

To make sure Wordfence isn’t unnecessarily slowing down your site, go to the Wordfence “Options” and verify two things:

• In the “Basic Options” section, uncheck Enable Live Traffic View if you don’t regularly use that feature
• In the “Scans to include” section, uncheck Scan images, binary, and other files as if they were executable"

​

Click to expand...

purity said:

Tomz updated Wordfence - WordPress Security Plugin with a new update entry:

Wordfence v7.7.1 Nulled



Read the rest of this update entry...

Click to expand...

Wordfence 7.8.0 is out! A huge thanks to our quality assurance team, our team of developers and our ops team for planning, implementing and releasing Wordfence 7.8.0. This release has several fixes to make Wordfence even more robust, and includes a fundamental change in the way our signup works.

The full announcement is in this email and also appears on the official Wordfence blog.

Since our launch in 2012, the signup flow for Wordfence has not required you to leave your own WordPress installation and come to our website. We briefly required this, but removed it 10 days after launch.

Wordfence has grown to a community of over 4 million active websites and a very large number of paying customers. Wordfence is now downloaded over 30,000 times every day. Today we spend a huge amount of money on providing the services that our free and paid community needs to stay secure. Privacy laws have also changed profoundly since 2012.

Scaling up our operations has required us to get better at capacity planning, which means knowing how many installations we’re getting, how many are bots or spam, who is communicating with our servers during a scan, and whether it is a real website running Wordfence, a nulled plugin or someone simply using our resources to power something unrelated to Wordfence.

Privacy laws have also added the need for us to be able to communicate with our free customers to alert them to privacy policy and terms of use changes.

This has required us to adjust our signup flow to match other popular plugins out there, like Akismet. Many customers may find this is a clearer signup workflow because we no longer need to shoehorn a complex user experience into a set of modals on a site where we don’t control presentation.

This change will not disrupt any of our existing free or paid customers. If you have a free API key that Wordfence automatically fetched when you installed it, that key will remain valid and your site will continue uninterrupted. If you have a paid Wordfence API key, your key will continue to work without disruption. We are not requiring any existing customers to visit our site to install a new key.

The only users this affects are new free Wordfence installations. The installation process is quite simple. You install Wordfence and are directed to our site. You can choose a paid or free option. If you choose the paid option, you’ll go through our checkout process as usual. If you choose free, we’ll email you your key. The email includes a button that you can click to automatically take you back to your site where your key will be automatically installed. The email also includes your Wordfence key in case you need to manually install it.

A side benefit of this new process is that our free customers will now have a record of their API key in their email inbox for future reference.

Click to expand...