This is only a tiny plugin with one php file that probably needs to be changed, and would be an ideal candidate to showcase the new Security page in the admin panel of CP v1.1.0
The plugin still works with this version, even though it hasn’t been updated for 2 years and I use it on all my sites. It is a last-resort backstop that catches people trying to guess the login details, when all my other plugins missed it. It even catches people trying to get in via the back door, and not the actual login form.
I particularly like it because it permanently blocks the IP address in .htaccess ( I set it to 3 attempts) and sends me an email letting me know.
I read the information for developers using the Security page, but don’t feel confident enough to try modifying it myself.
If someone could fork it, then I can write a post at ClassicPress.club with screen shots of how it is displayed in the admin panel.
I think it would help to have an example plugin, especially a small but useful one such as this.
The plugin did not work. It was in the list of installed plugins, and showing as active, but could not be accessed from Settings (or anywhere else) in the admin panel, and nothing showed under Security.
The .htaccess file did show the code block ready for blocked IP’s.
I was then unable to activate the original plugin by uploading it. There was a “format error” message. It installed and activated okay by downloading it from the plugin page though.
For what it’s worth, I see the original GitHub page is showing the structure for a development version. It contains files that are not present in the actual v1.5.3 plugin zip file.
I also notice under “Issues” that this plugin only works with Apache and not Nginx, so maybe it’s not a good plugin to use as an example.
No, no warnings or error log entries. It just seemed to be invisible to the admin panel.
I did notice the screen went blank when activating the plugin, with no details showing what was in progress, as you usually get.
One of life’s many mysteries.
Maybe something remained in the database when I uninstalled the original plugin. You wouldn’t have had that problem. I might try again and do a search of the records before installing your version.
Looking at the GitHub page files and those on my website, there are significant differences. I downloaded the zip file from the “Clone or Download” dropdown. I think I should have downloaded v1.5.2 from the “Releases” page, even though it’s dated 2015. That file is actually your new one and not the original v1.5.2 one.
That is not clear to someone who doesn’t understand GitHub.
Okay, I finally got it to work before my server crashed on me. I downloaded the version from “Clone or Download” and renamed the folder before activating the plugin.
It showed under “Security” and I could configure it.
So why is the folder not correctly named initially?