开发者 | jsmcm |
---|---|
更新时间 | 2015年10月16日 02:03 |
PHP版本: | 3.5.1 及以上 |
WordPress版本: | 3.6.0 |
版权: | GPLv2 or later |
版权网址: | 版权信息 |
country-code-failed-login
folder to the /wp-content/plugins/
directoryThis may happen if your web hosting company has not configured their server to handle SOAP. The first thing you should do is ask them why! Then to access your login form go to your wp-login.php form and add the ccfl=off parameter, eg, http://yoursite.com/wp-login.php?ccfl=off If this seems confusing, please go to http://www.phpwebhost.co.za/wordpress/country-code-failed-login/ccfl.php for more info and we'll help you get in!
If your blog allows registrations and logins from more than a single country, then no, this plugin will not be suitable as your users outside of your country may be blocked.
That depends on where your multiple users are. This is really more of a multiple country question. If your blog allows registrations and logins from more than a single country, then no, this plugin will not be suitable as your users outside of your country may be blocked.
This shouldn't really happen, provided that you've set your own country in the settings screen. This plugin will not block the country you select there
As server admins we see huge numbers of attacks on the wordpress login screen. These brute force attacks are a real threat to your wordpress site. We've seen up to 2000 attacks from almost as many different IPs on a single site per hour recently. This is not about being "nasty" to other countries, but lets face it, if your in a particular country do you really need to provide access to your login form to other countries?
Its true that if you were the only person using this plugin, it would not help much. However, as this plugin is used by more and more sites its very likely that bad IPs will be in the block list before they even get to your site, in which case they will not be able to access the wp-login.php form, so yes, it helps.
Nothing... The plugin won't log bad IPs and it won't block IPs either. Its essentially the same as deactivating the plugin