Support

Don, I understand your point of view. For the record, I have to declare the factors behind my decision not to publish a new version or replace the package:

• Once a release is out, it's out. I don't go ahead and replace the installation package of a release unless I have done something stupid and uploaded a non-installable package, the wrong version and so on. The thing is that if I release what essentially is a new version under the same version number it's a support nightmare. If someone tells me that he has Admin Tools Pro 2.4.3 and that feature doesn't work how can I possibly know if he has the affected version or the fixed one?
• The bug is minor. There is a viable workaround. It's not the end of the world. If I was releasing a new version every time I fix a small bug there would be one version every three days, sometimes even three to four versions every day.
• You would be surprised at the number of people who get pissed whenever I release a new version unless an arbitrary "long" period has elapsed. I understand their point of view. If you have dozens of sites, even one click updates might take you half an hour.

It is due to all of the above that I devided not to replace the file in the CDN or publish a new release.

Now, regarding your comments:

I have never before disagreed with you, and I don't wish to be disagreeable, period. It's just that, in the case of the Websites I maintain, the ability to blacklist IP addresses is an important feature. Whether anyone believes it or not, the server logs indicate that blacklisting stops an incredible amount of machine-gun style hacking/hijacking attempts, primarily from IP addresses listed as originating in the Russian Federation and the PRC. I really, really hate to castigate any country, but it is as it is.

Please read again my post in the other thread. I specifically talked about "long term IP blacklisting". Please note that it's long term, not IP blocking in general. Bear with me for a while. Long term means that you set a block on this IP and then you forget about it for months. The attacker will change his IP tomorrow or in 10 days max (I have the mind-blowing amount of log data from my site to back up my claim). What you achieve with a manual, long term block is ending up slowing down your site (each entry requires a couple of milliseconds to process, times 2000 and you have a HUGE delay on each and every page loaf) or block potentially legitimate visitors.

Do you know what the best approach is? Use the automatic IP blocking. This is EXACTLY what it's designed for. When someone trains the crosshairs of a bot against your site Admin Tools detects it and blocks the IP. The more the bot tries, the quicker it gets banned. The more they persist, the longer they get banned. And the ban auto-expires, solving the issues which come with excessive IP banning. See? I agree with you and I actually provide you with the right tool to do the job. Just use it ;)

So I have gone into each and every site and modified the log.php file to remove the typo you pointed out. If this will be a continual thing, well, there's that, too.

That's a solution, too, but I'm afraid that you are using a sledgehammer to put a nail in the wall. Just because you can doesn't mean you should. Use the proper tool for the intended task. That's what I was trying to say, but I was overly laconic in that other thread. Sorry! I should have explained it better.

Thanks, Nicholas. I thought that a quick switch or modification to the SDN/download would be feasible, but I often have incorrect thoughts...No problems.

I had to learn first hand why that's a bad idea, don't worry :)

As for the rest, I do use Automatic IP Blocking. In fact, I've grown so tired of the crap put out by so many, many despicable people that I set it to automatically block an offending IP address at the first attempt, and I extend the blocking period quite a bit.

Precisely my thought process before I implemented the auto-block feature ;) Since my company was based in Greece and, now, in Cyprus I am an often receiver of hacking attempts from Turkey. It's a well known cat and mouse game between the Greek and the Turkish hackers. I was so sick of blocking IPs from Turkey manually that I implemented a feature to automate the process.

PS: You'd better make that something like 2 attempts within a minute. Legitimate users will eventually find a way to screw up and trigger a false positive. Of that I am perfectly sure ;)