gabbuz

Thank you Jeremy, hope to see the new configuration page in Jetpack 3.5; until then, I’ll keep the BruteProtect plugin on.

I would have another question about Protect feature: does the Protect feature provide a control against XMLRPC bruteforce attacks, insted of just the login-page attacks?

Thanks Jeremy for the feedback, but what happens in case a blog is not connected to Jetpack (maybe because the user doesn’t care about it)? Would the Protection feature be active anyhow like with BruteProtect?

The most interesting feature would be transfer totally the Protection feature settings into the Jetpack Network menu (from <website URL>/wp-admin/network/admin.php?page=jetpack-settings), exactly like BruteProtect works now.

What do you think?

Unfortunately I can’t since I’m on a WordPress MU live, but I’ll wait for the new version release to see if it fixes the issue.

Thank you Chouby!

It works perfectly now.

Thanks ??

I commented the check at line 53 and the plugin started working again.

Is there a way to check if WPML is active also as a whole network plugin?

Maybe this?
https://codex.www.ads-software.com/Function_Reference/is_plugin_active_for_network

For the first, I can’t find the .htaccess you’re talking about.
Is the .htaccess created automatically by the plugin?

Is the second bug maybe related to the upload folder? Maybe the media space for the main blog is counted in the upload root folder?

Great to hear it, hope to see that update soon ??