wpsnoop: fix Brute Force Login Protection plugin conflicts, errors & issues

When the plugin Brute Force Login Protection conflicts or throws a PHP error we hope wpsnoop can help you to fix the issue quickly.


Discover which shortcodes wp-options PHP functions database tables and files are created by Brute Force Login Protection, plus learn which plugins and/or themes could be in conflict with Brute Force Login Protection.


Troubleshooting theme and plugin conflicts is easier when you know what Brute Force Login Protection leaves behind after uninstalling it from a WordPress installation, there is a list down below for your convenience.

Expert advice is recommended if you are not technically proficient with PHP, MySQL etc. View support options for Brute Force Login Protection


What does Brute Force Login Protection version 1.5.3 add to WordPress? Answers Here.

This is an automatically generated report - it is possible for Brute Force Login Protection to perform differently in your installation, previous versions before 1.5.3 may have created a different set of shortcodes, used different function names or could have created entirely different database tables to store settings and operate. This is not an exhaustive list but shows how version 1.5.3 of Brute Force Login Protection behaves when installed and removed on a clean installation of WordPress.

We have not tested individual shortcodes, features or settings of this plugin but instead have concentrated on the potential for obvious errors and conflicts which can occur, if you need help with the plugin in your local installation you can get WordPress help and support for Brute Force Login Protection by clicking here.

Our testing covered the free version of this plugin there may or may not be a paid version or premium version available for purchase that unlocks additional features and could behave in a slightly or very different manner.

Which new files does Brute Force Login Protection add to WordPress?

This section will populate with a table showing an icon, size and filepath.

Type & Path Size Conflicts
.htaccess 157.00B The .htaccess file has potential conflicts with at least 76 other plugins or themes.
wp-content/plugins/brute-force-login-protection/ 55.67kB No known conflicts with other themes or plugins.
wp-content/plugins/brute-force-login-protection/brute-force-login-protection.php 18.35kB No known conflicts with other themes or plugins.
wp-content/plugins/brute-force-login-protection/includes/ 19.55kB No known conflicts with other themes or plugins.
wp-content/plugins/brute-force-login-protection/includes/htaccess.php 9.33kB No known conflicts with other themes or plugins.
wp-content/plugins/brute-force-login-protection/includes/settings-page.php 10.23kB No known conflicts with other themes or plugins.
wp-content/plugins/brute-force-login-protection/languages/ 14.03kB No known conflicts with other themes or plugins.
wp-content/plugins/brute-force-login-protection/languages/brute-force-login-protection-nl_NL.mo 5.83kB No known conflicts with other themes or plugins.
wp-content/plugins/brute-force-login-protection/languages/brute-force-login-protection-nl_NL.po 8.20kB No known conflicts with other themes or plugins.
wp-content/plugins/brute-force-login-protection/readme.txt 3.74kB No known conflicts with other themes or plugins.

Which new shortcodes does Brute Force Login Protection add to WordPress?

Which new database tables are created by the WordPress plugin Brute Force Login Protection?

Which new options are added to the wp-options table by Brute Force Login Protection?

What new PHP functions does Brute Force Login Protection declare when it is active?

Using Brute Force Login Protection from the command line with WP-CLI

The following commands are provided for convenience and should only be used if you understand how WP-CLI works. These commands refer to a single WordPress instance and may need to be modified if you are working with a Multisite installation.


How to install Brute Force Login Protection from the command line with WP-CLI

Navigate to the root of your WordPress installation and type the following command:

wp plugin install brute-force-login-protection


How to activate Brute Force Login Protection from the command line with WP-CLI

To immediately activate Brute Force Login Protection after WP-CLI downloads the latest version you can use the following command:

wp plugin install brute-force-login-protection --activate


How to reinstall Brute Force Login Protection from the command line with WP-CLI

To force a reinstallation of Brute Force Login Protection which overwrites the current plugin without asking for confirmation you can use the following command:

wp plugin install brute-force-login-protection --force


How to update Brute Force Login Protection to the latest version from the command line with WP-CLI

wp plugin update brute-force-login-protection


How to delete Brute Force Login Protection from the command line with WP-CLI

wp plugin delete brute-force-login-protection

Where can you download earlier versions of Brute Force Login Protection?

Whenever possible you should use the latest version of plugins and themes, however if you have recently updated and discovered that you need to install an earlier version you may be able to download other versions of Brute Force Login Protection from the WordPress repository by visiting this link.

Please note that installing earlier versions of a theme or plugin is not generally a recommended course of action for most users and could re-introduce security, stability or other issues in Brute Force Login Protection

About our testing enviroment

Tests were conducted using Apache 2.4.29, PHP 7.2 on Ubuntu 18.04, MySQL 5.7.33 and WordPress 5.9

It is very possible that different versions of PHP such as PHP 8.0, PHP 7.4, or PHP 7.3 could behave differently with Brute Force Login Protection. Different versions of WordPress could implement the features of this plugin in slightly different ways as well.