I finally found a good WordPress anti-spam plugin that is free and does not get affected by caching plugins. Try to look for anti-spam plugins int he WordPress admin console and the first few results given to you are not really free.
Sure, they list it as free but once you start using it, it gets problematic and they do not really work flawlessly. Later on, you will find out that the free version is actually crap and you need to buy the license in order to get the plugin working.
Antispam Bee however, is TOTALLY free and straightforward. Just add, install and activate. That’s it!
The plugin itself has quite a number of options to make it flexible according to your choosing. However, if you want to go for the default settings, they still work the way you want it to: block unnecessary comments.
Even if you are using caching plugins it won’t get affected.
Easy and extremely productive spam-fighting plugin with many sophisticated solutions. Try it!
After being hit with malware that took advantage of some holes in old WordPress versions, I finally was able to solve the iFrame malware problem that had dogged a few of my other blogs.
I wondered why Sucuri always displays those same malware error messages even though I already cleaned everything. I thought Sucuri was nuts. So yes, their plugin actually bases the results on cached results.
If you want to have the updated results of Sucuri’s scan of your blog, make sure you click the RE-SCAN button in their site so the cached result will be the latest one that the plugin will use its report on.
While browsing through some of my folders, I noticed that wp-includes and all its subfolders exposed the file listing. This is a bad thing. Nobody should ever know what it inside your site’s folders. The plugin Silence is Golden Guard helped free my blog sites totally of those malware iframe error messages.
This plugin basically adds an index.php file in every folder of your blog site. There is nothing more this PHP file can do except just idle itself and show a blank screen in the browser whenever someone attempts to browse folders in your blog.
I believe the developer should at least put another option to have index.html instead of index.php. One may never know if the blog may get infected again. At least those PHP code will be useless inside an HTML file.