Wordfence Security Premium

Please update Wordfence Security Premium 7.9.0 to WordFence 7.9.1. @Steve

1 Like

Wordfence Security Premium has been updated to 7.9.1.

When i click on “Start New Scan” it is giving erroe, please check screenshot.

Hello @Annahlabbas,

Thanks for reporting this issue.

The file has been replaced.

When i do a “New Scan” it runs and giving me a warning that the plugin files are modified. Particularly it is giving “file changed” warning for “wordfence plugin files”

Is that safe to ignore this?

Check screenshot…,

Yes, its fully safe to ignore.

We had to do some modifications to the code to make the pro version working :wink:

Wordfence Security Premium has been updated to 7.9.2.

Hi, I have 1 question before downloading this plugin.
I haven’t used it yet, so can it be used for beginners?
I can’t go to " All options ", does that mean I can’t activate it?

1 Like

Hi @thinkingforward,

Thanks for letting us know!

@Steve → can you please check this instance? Thanks!

2 Likes

The file has been replaced now.
install first Wordfence free and get a free license to your email. Then install Wordfence Premium and replace with the existing one. that’s all

1 Like

Please update Wordfence Security Premium 7.9.2 to 7,9,3. @Steve

We would LOVE to update to its latest version, but we encountered an issue with the activation with its latest version. We’re unable to bypass the security in its latest version, as it’s making a lot of server API calls. We will update the file as soon as possible once we got a solution for this.

Please update Wordfence Security Premium 7.9.2 to 7.9.3. @Steve

Wordfence Security Premium has been updated to 7.9.3.

So you found a workaround for this? :sunglasses:

Hey Alex,

The plugin is working 100% and it has been updated to it’s latest version 3 hours ago.

Are you experiencing any issues so far?

:sunglasses: I love the vault! Thank you Festinger!

We love you too as a customer <3

Please update Wordfence Security Premium 7.9.3 to 7.10. @Steve

We would LOVE to update to its latest version, but we encountered an issue with the activation with its latest version. We’re unable to bypass the security in its latest version, as it’s making a lot of server API calls. We will update the file as soon as possible once we got a solution for this.

Meanwhile, please have a look at this thread which explains the entire process. :slight_smile: